Knowledge Graph Ingestion Prioritizes Curation, Identity Decisions

Vaibhav Dangaich, Kevin Lewis, Kundeshwar Pundalik· August 12, 2026 View original

Key takeaways

  • Identity decisions in knowledge graphs are critical and irreversible if incorrect.
  • A multi-stage identity resolution process, including a "record-identity ladder," is essential.
  • Human oversight in entity resolution is crucial to prevent data corruption.
  • "Curate before you connect" is a vital principle for maintaining data integrity in knowledge graphs.

Who benefits

Data ManagementGovernmentFinanceHealthcareLegal

Summary

This paper details an ingestion and ontology-tagging layer for a production knowledge graph, emphasizing that identity decisions are critical and irreversible. It describes a record-identity ladder and canonical-name key for de-duplication, arguing for human oversight in entity resolution to prevent data corruption.

Building a robust knowledge graph involves more than just extracting entities and relationships; the crucial step is deciding their identity and how they connect. This research highlights that identity decisions are fundamentally destructive if incorrect, as merging records erroneously can lead to irreversible data corruption. The paper describes a specific ingestion and ontology-tagging layer used in a production knowledge graph containing over half a million entities from government documents. It introduces a "record-identity ladder" that determines sameness based on identifiers, names, and context, rather than just name similarity. A coarser canonical-name key is then applied for automatic merging of records with exact matches. The authors advocate for a policy where entity resolution only flags candidates for human review, rather than automating merges. This approach stems from an incident where an erroneous merge corrupted records, underscoring the need for careful curation before connecting data to prevent undetectable errors and maintain data integrity.

Why it matters

Data architects, knowledge graph engineers, and data governance professionals can learn critical lessons about managing data identity and preventing corruption in complex data integration projects.

How to implement this in your domain

  1. 1Establish a clear "record-identity ladder" for de-duplication based on multiple attributes.
  2. 2Implement a canonical-name key for initial, highly confident automatic merges.
  3. 3Design a curation queue for human review of all potential entity merges flagged by automation.
  4. 4Prioritize "curate before you connect" in knowledge graph ingestion workflows.
  5. 5Develop robust error detection and rollback mechanisms for identity decisions.

Original post by Vaibhav Dangaich, Kevin Lewis, Kundeshwar Pundalik

"arXiv:2608.10644v1 Announce Type: new Abstract: Extraction produces candidate entities and relationships; writing them into a graph is where identity is decided, and identity decisions are destructive in a way extraction errors are not. A wrong type can be corrected later, but tw…"

View on X

Originally posted by Vaibhav Dangaich, Kevin Lewis, Kundeshwar Pundalik on X · view source

Want to go deeper?

Turn these trends into skills with Learnijoy's hands-on AI & tech courses.

Explore courses