Triple

T35404658
Position Surface form Disambiguated ID Type / Status
Subject Central Contractor Registration E1023333 entity
Predicate instanceOf P0 FINISHED
Object U.S. federal government database C9601 CONCEPT FINISHED

How this triple was built (1 step)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

CD Concept disambiguation gpt-5-mini-2025-08-07 
Target class: U.S. federal government database
Context triple: [Central Contractor Registration, instanceOf, U.S. federal government database]
  • A. United States federal government database chosen
    A United States federal government database is an official, centrally managed digital repository that stores, organizes, and provides controlled access to data collected or maintained by federal agencies for governance, regulatory, research, and public transparency purposes.
  • B. federal government database
    A federal government database is a centralized, secure digital repository used by national government agencies to store, manage, and retrieve official records, data, and information for administrative, regulatory, and public service purposes.
  • C. federal government database
    A federal government database is a centralized, electronically managed collection of structured data maintained by national government agencies to store, process, and retrieve information for administrative, regulatory, and public service purposes.
  • D. United States government dataset
    A United States government dataset is a structured collection of data produced, maintained, or funded by U.S. federal, state, or local government entities for public use, analysis, and decision-making.
  • E. federal data repository
    A federal data repository is a centralized, government-managed system for collecting, storing, and providing controlled access to official datasets for analysis, oversight, and public use.
  • F. None of above.

Provenance (1 batch)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69f76df43ca4819098711ca4370f1bb9 completed May 3, 2026, 3:47 p.m.
Created at: May 3, 2026, 4:03 p.m.