To forget is to know
Not as glorious as acquiring it but just as important.
We are obsessed with knowledge graph extraction pipelines, entity resolution, ontology alignment, ETL, CDC and I admit, I help companies doing precisely that. But knowledge has a shelf life: contracts expire, regulations get superseded, business is dynamic, not to mention the geopolitical shifts. That authoritative product hierarchy from last year is now three reorgs stale, but the KG/ontology is still serving it with full confidence, right next to yesterday’s facts.
RDF has no native notion of decay, LPGs let you slap a timestamp on an edge and then ignore it forever. Neither community has a good answer to the question: when does a fact stop being true, and who tells the graph? The who matters here: do companies have business flows to forget things? The same is obviously true for SQL data but cascading deletes are a lot easier there, the foreign keys mechanics is a blessing we do not have in KGs.
The result is a familiar failure mode: the graph doesn’t become wrong all at once. It accumulates errors quietly. A knowledge graph that’s 90% accurate but you don’t know which 90% is maybe worse than no graph at all. Downstream reporting and bots use the stale info into confident answers.
To be precise, forgetting is not data loss. Forgetting is an inference problem: provenance, temporal validity, confidence that degrades unless evidence renews it. A fact extracted from a 2019 PDF should not carry the same weight as one from last quarter’s filings yet in most triple stores, it does. We engineer elaborate machinery for adding knowledge, we hardly ever create the machinery for letting it go.
Yes, I know, the many AI memory systems out there (Mem0, Graphiti…). These tools are per-agent, per-user, conversation-scoped. Enterprise knowledge is cross-team, cross-document, governed, versioned, and contested. Nobody’s compliance department is going to sign off on “the graph is whatever the agent remembered.” The moment you need provenance, temporal validity, access control, or two agents sharing a consistent world model, you’ve left the design envelope of a memory layer entirely. Memory is what was said. Knowledge is what survives scrutiny. Conversation versus science, they are related but not the same.
hashtag#KnowledgeGraphs hashtag#Ontology