Co-author

Co-author is your AI-powered assistant for accelerating knowledge graph refinement. Give co-author instructions on what you would like to be updated before reviewing and testing these changes.

All features delivered by Rainbird Labs are beta. They may contain bugs, are subject to change and are not covered by our platform SLAs. Your feedback can help shape development.

Getting Started

Within the Rainbird Studio open the Co-author chat agent in any knowledge graph and write your instructions.

Updates will be applied to the graph and an explanation of the change provided in the Co-author chat panel.

It is advised to create a snapshot of your graph by versioning it, prior to changes as undo functionality is not currently available.

Use cases

Updating the graph

  • Quickly add multiple instances: "Add instances for every country in Europe"

  • Create facts: "Update the graph to include facts stating the national languages for every country in Europe"

  • Create test data: "Add facts for John, Paul, George and Ringo, using different data for each person"

  • Iteratively expand the knowledge graph: "Expand the graph so it also factors in the native language spoken by the person's parents."

  • Update question wording: "Can you improve the question wording for all relationships that can ask questions?"

  • Copy rules between relationships: "copy the rule on relationship [relationship name] onto [relationship name], ensuring it is updated to reflect the new relationship"

We recommend that you version your graph first, in order to create a point to restore to.

Searching the graph

  • "Can you list all relationships that can ask questions?"

  • "Which relationships are in a group?"

  • "Can you list all date concepts?"

Explaining the graph

  • "Can you explain the rules on the [name] relationship?

  • "Can you explain what this graph does?"

Co-author supports multiple modes, many of which are experimental.

For optimal results we recommend leaving it on the default mode.

Versioning

It is recommended to version your knowledge map between Co-author requests, including a comment of the changes introduced.

This provides an opportunity to easily restore an older version if you want to undo a Co-author change. Information on versioning can be found in the Academy.

Versions can only be created when there are no errors in the knowledge map. There may be some known errors introduced by Co-author, which are mentioned below.

Important Information

Data Security

Co-author operates using third-party AI services (Anthropic and OpenAI). Please ensure shared information is suitable for external processing.

Any request made via Co-author shares the Knowledge Map with the LLM provider.

Limitations

  • Token limits apply. For large content and/or large knowledge maps, limits may be reached and incomplete RBLang returned resulting in error.

  • The chat history is not currently shared with each Co-author request (to reduce token usage), therefore prompts such as "No I didn't mean that, can you change it to deny" will not have context of the messages before it.

  • Service may be interrupted during peak periods.

  • Varying behaviour: LLMs are not deterministic so you will likely see different responses when testing the same content.

  • Map layout: A new map will auto-layout, but if updates are being made to an existing map the concepts will be placed in the centre and require manually rearranging.

  • RBLang errors: whilst we continue to make improvements, there are some of the common errors created by Co-author. You can ask Co-author to fix some of these (copy and paste the error to Co-author), but some may need to be fixed manually. Some of these can be fixed in the Editor UI, whilst others will require fixing directly in RBlang (accessed via the </> code panel).

Common Co-author errors

  1. Rules that reference instances that don’t exist

    1. Identify the relationship of this rule, identify the concept it’s attached to then add the instance to this concept.

  2. Incorrect use of variables in the rule header

    1. You may see Subject=”%S” or Subject=”%PERSON” in the rule header (the start of the rule). This is invalid, as variables can only be used in conditions. Remove any subject and/or object from the rule header that contains a variable. If it used a custom variable (e.g. %PERSON) it may also have used this in the conditions below, when it should use the specially designated variables of %S for the subject or %O for the object. These will need to be updated.

  3. Relationships referencing concepts that don’t exist

    1. Often these tend to be called something generic like String, Date, Number or Truth. You will need to review the graph, determine what the concept should be called, create one with this name then update the relationship to refer to your new concept.

  4. Invalid expressions

    1. Unsupported expressions can sometimes be generated, which can be manually fixed in the UI. Use our documentation to help create a valid expression. Where an expression contains multiple OR conditions, this can sometimes indicate the rule needs to be split into multiple rules. You can duplicate the rule and modify them, or prompt Co-author to separate these rules into distinctive rules.

Once fixed and you can save successfully, create a version of this so you can return to it if required.

Last updated