Knowledge graph

A knowledge graph stores facts as entities and the relationships connecting them, a person, an organization, a works-at relationship between them, rather than as blocks of text to search. Each fact carries provenance back to the document it was drawn from, so a graph is not just a diagram, it is a queryable, source-linked record.

Regulated investigations, know-your-customer checks, ownership questions, are relationship questions by nature. Without a knowledge graph, an analyst reconstructs those connections by hand, reading document after document and keeping the map in their head.

Which vendors share a registered address with this counterparty is a graph query across shared attributes and relationships, not something a keyword search over documents can answer directly.

In Dynamiq, a Knowledge Base can extract entities and relationships into a graph alongside its vector store, constrained by an editable ontology, entity types, relationship types and the patterns allowed between them, so extraction stays on-schema rather than free-form. Every fact remains traceable to the document and the access list it came from.