Triple
T38701576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Chief Data Officer Community |
E950153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government data leadership network |
C65977
|
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: government data leadership network Context triple: [Federal Chief Data Officer Community, instanceOf, government data leadership network]
-
A.
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.
-
B.
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.
-
C.
government information center
A government information center is a public facility or service that provides citizens with access to official information, resources, and assistance regarding government programs, services, and regulations.
-
D.
policy-relevant data compendium
A policy-relevant data compendium is a curated, structured collection of datasets and indicators organized to inform, support, and evaluate public policy decisions on specific issues or sectors.
-
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. chosen
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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:33 p.m.