Skip to main content
GoldenGraph builds an own-your-KG knowledge graph from text: text → LLM extraction → GoldenMatch entity resolution → a durable, bi-temporal store. Entity resolution is the differentiator. Duplicate surface forms across documents collapse into one durable entity — the step most GraphRAG frameworks do badly, because they treat resolution as string matching rather than as the entity-resolution problem it actually is.

The stages

Bi-temporal by construction

The store records both valid time (when a fact was true in the world) and transaction time (when the graph learned it). as_of(valid_t, tx_t) returns the graph as it was believed at a point in time — which is what makes a KG auditable rather than merely current. A correction does not erase what the graph previously asserted; it adds a new transaction over the same valid-time span.

Relationship to goldenmatch-kg

GoldenGraph is a complete KG builder. GoldenMatch KG is the opposite shape: it drops goldenmatch’s resolution into someone else’s KG pipeline (neo4j-graphrag, LlamaIndex, Graphiti). Use GoldenGraph when you own the pipeline; use goldenmatch-kg when you are adopting one.