Triple
T22674643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IDIS |
E560315
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal grants management system |
C357
|
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 grants management system Context triple: [IDIS, instanceOf, federal grants management system]
-
A.
library grant program
A library grant program is a structured funding initiative that provides financial support to libraries for projects, resources, services, or infrastructure that enhance community access to information, education, and cultural enrichment.
-
B.
federal conservation program suite
A federal conservation program suite is an integrated set of government-administered initiatives, policies, and funding mechanisms designed to protect, restore, and sustainably manage natural resources and ecosystems across jurisdictions.
-
C.
federal government program
chosen
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.
federation of government agencies
A federation of government agencies is a collaborative structure in which multiple semi-autonomous public organizations coordinate policies, resources, and operations to achieve shared governmental objectives while retaining their individual mandates.
-
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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:10 p.m.