Triple
T13105518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFDA.gov |
E310832
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal programs database |
C8594
|
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 programs database Context triple: [CFDA.gov, instanceOf, federal programs database]
-
A.
federal government database
chosen
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.
-
B.
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.
-
C.
federal government program
A federal government program is an organized set of activities, services, or regulations funded and administered by the national government to achieve specific public policy goals.
-
D.
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.
-
E.
data-driven government program
A data-driven government program is an initiative that systematically collects, analyzes, and applies data to design, implement, and continuously improve public policies and services for better outcomes and accountability.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:05 p.m.