Triple
T5678519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CUI Registry |
E125144
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal information resource |
C1191
|
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: federal information resource Context triple: [CUI Registry, instanceOf, federal information resource]
-
A.
information resource
chosen
An information resource is any identifiable source that stores, provides, or transmits data, knowledge, or content in a form that can be accessed, interpreted, and used by humans or systems.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
federal information sharing initiative
A federal information sharing initiative is a coordinated program through which federal agencies and authorized partners securely exchange data, intelligence, and best practices to improve decision-making, policy implementation, and national security.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:44 p.m.