Knowledge graph

The knowledge graph holds the entities found in your sources (people, organizations, products, places and more) and the relations between them. Each project has one graph, fed by all its knowledge bases.

Grey builds it during ingestion, in each job's Graph stage, for knowledge bases whose ingestion settings have Extract entities and relations turned on. It's on in the Balanced, High accuracy and Auto presets. To build the graph:

1. Set a processing model in Settings → General. Extraction runs on it.
2. Make sure Extract entities and relations is on in the knowledge base's ingestion settings.
3. Add sources, or re-ingest the ones already there.

Without a processing model, ingestion still finishes, but the graph isn't updated. Re-ingesting a source replaces what Grey found in it earlier.

Every entity has a name, a type, optional aliases and a description, a source and a confidence. The source says where it came from: Grey (extracted from your sources), Forms (added from Geiger Forms submissions) or Manual (added by hand). The confidence is how sure the extraction was, as a percentage.

A relation joins two entities with a relation type, such as works_at or part_of. A mention records that a source talks about an entity, with the page when Grey knows it.

The project's ontology lists the types. Grey extracts only those entity and relation types, guided by each type's description, and keeps entities it's at least 50% confident about. Anything that fits no type is filed as Other or related_to.

Pipelines can use the graph when they answer. A pipeline's Graph setting decides when; see Pipelines and model providers.

Knowledge Graph → Graph Explorer draws the graph. Each dot is an entity, colored by its type and sized by how many relations it has, and each line is a relation. Click an entity to open its details, and click empty space to close them.

• The type chips narrow the graph to the types you select; select several to combine them.
• The knowledge base filter keeps entities mentioned in that knowledge base's sources.
• Search entities matches names and aliases and lists up to eight matches. Click one to select it and center the view on it.
• 2D and 3D at the top left switch the view. 3D is the default.
• The + and − buttons at the bottom left zoom, and the button at the top right fits the whole graph in view.
• Graph forces opens sliders for Center force, Repel force, Link force and Link distance, with a button that restores their defaults.

The graph draws at most 500 entities, keeping the most connected ones, and says how many it's showing when it hides some.

Click an entity in Graph Explorer or the Entities list to open its details: its type, description, aliases, source and confidence.

• Relations: every relation to or from the entity. To add one, pick a Relation type and a Target entity, then choose the + button beside them. Remove a relation with the trash icon beside it.
• Mentioned in: the sources that mention the entity. Click one to open it in Sources.

Ask about this opens Chat with a question about the entity already typed in the message box, ready to send or change. Edit opens the entity's form.

Adding or removing relations and editing need the Edit the knowledge graph permission, which every built-in role except Viewer has. Without it, those controls don't appear.

Knowledge Graph → Entities lists the graph's entities. The figures across the top count the Entities, Entity types, Relations and Possible duplicates.

Each row shows the entity's name and type, how many relations and mentions it has, its source, its confidence and when it was last updated. Search by name or alias, and click a row to open the entity's details. Each row's ⋯ menu has Edit and Delete if you can edit the graph.

The list shows 25 entities a page; switch to 10, 50 or 100 at the bottom. The Possible duplicates tab lists entities that look like the same thing.

To add an entity by hand, choose Add entity on Graph Explorer or Entities, fill in the form and choose Create entity.

• Name and Type: required.
• Aliases: other names for the entity. Press Enter after each one.
• Description: optional notes.

Entities you add show Manual as their source. To change one, choose Edit in its ⋯ menu or its details, then Save changes.

To delete an entity, choose Delete in its ⋯ menu. Grey asks you to confirm first. The entity leaves the graph, its relations and mentions are left pointing at nothing, and it can't be restored from Grey. To combine two entities instead, merge them.

All of these need the Edit the knowledge graph permission.

Grey flags entities as possible duplicates when they have the same type and their names match, or one's name matches the other's alias. Names are compared without case, accents, punctuation or a trailing Inc, Ltd, LLC, Corp or Co.

To merge a group:

1. In Knowledge Graph → Entities, open the Possible duplicates tab.
2. Choose Merge on the group.
3. Click the entity to keep. It's marked Keep, and Aliases after merge shows the aliases it will have.
4. Choose Merge to confirm. The button names how many entities merge into which one.

The other entities' names become aliases of the one you kept, their relations and mentions move to it, and they leave the graph. Merging needs the Edit the knowledge graph permission.

Knowledge Graph → Ontology lists the project's Entity types and Relation types. A project starts with the entity types Person, Organization, Product, Location, Event, Concept, Document and Other, and the relation types works_at, part_of, mentions, related_to, located_in and created.

To add a type, choose Add type on either list. Name is required; pick one of five Colour options and add a Description if you like, then choose Create type. Grey reads each type's description when it extracts entities, so say what belongs in it. The pencil beside a type edits it.

The trash icon deletes a type that nothing uses yet, after you confirm. A type in use can't be deleted: hovering over its trash icon says how many records use it. Changes to the ontology apply to sources ingested from then on.

Managing the ontology needs the Manage the ontology permission, which Owners, Admins and Managers have.