Knowledge graphs and temporal paradoxes

Here’s a puzzle; was Pluto a planet?

In a knowledge graph, the answer depends entirely on when you ask the question and most graphs can’t tell the difference. This is the temporal paradox problem, and it’s weirder than it looks.

❖ The Retroactive Truth In 2006, the IAU demoted Pluto. But all those textbooks written before 2006? They were correct when written. A naive knowledge graph that just stores (Pluto - isA - Planet) and then updates it to (isA - DwarfPlanet) has silently erased a historical truth. Your graph doesn’t lie, it forgets.

❖ The Schrödinger CEO You ingest a corporate dataset. It says (Alice - isCEO - Acme Corp). Six months later you ingest a new dataset that says (Bob - isCEO - Acme Corp). Was Alice fired? Did she resign? Are both facts true (co-CEOs)? Or is one dataset simply stale? Without time-stamped edges, your graph is a superposition of realities. The moment you query it, you collapse it into a single answer and it might be the wrong one. Side note, such an exciting thought one could model quantum fields as a knowledge graph 🤔

❖ The Grandfather Contradiction Country borders change. (Kosovo - isPartOf - Serbia) was a valid triple. So was (Kosovo - isPartOf - Yugoslavia) before that. And now neither is true in the same sense. A graph that chains inferences across these facts can derive conclusions that were never simultaneously true.A logical grandfather paradox baked right into your ontology.

So how do you fix it? There are a couple of elegant solutions.

There is bitemporal modeling: track two timestamps on every edge: valid time (when was this true in the world?) and transaction time (when did you record it?). They’re not the same, and confusing them is the root of most graph temporal bugs.

You have named graphs + RDF*: wrap facts in a context node that carries provenance, validity windows, and confidence. Query the context, not just the triple.

There is event-based reification: instead of (Alice - isCEO -Acme), model the appointment event: a node with a start date, an end date, and a source. Relationships become first-class citizens.

Some databases like TerminusDB and TigerGraph’s temporal extension, have temporal query layers. They let you query “what did the graph believe on date X?” hence separating knowledge history from world history.

The insight is this: a knowledge graph without time is a photograph pretending to be a film. Reality is dynamic, it’s a process, not a state. The most dangerous knowledge graph is one that looks authoritative but has silently flattened four dimensions into two.