Triple
T35548158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USAspending.gov |
E1027275
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal spending 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 spending database Context triple: [USAspending.gov, instanceOf, federal spending 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 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.
-
D.
federal government
The federal government is the central governing authority of a nation that holds supreme power over national affairs, such as defense, foreign policy, and regulation of interstate matters, while sharing sovereignty with regional or state governments.
-
E.
government budget
A government budget is a financial plan that outlines a government's projected revenues and expenditures over a specific period, typically one fiscal year, to achieve its economic and policy objectives.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.