Triple
T36828536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal District Commission |
E910073
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal planning body |
C65485
|
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 planning body Context triple: [Federal District Commission, instanceOf, federal planning body]
-
A.
U.S. federal planning instrument
A U.S. federal planning instrument is an official document or tool used by federal agencies to set goals, allocate resources, and coordinate actions over a defined time horizon in support of national policies and programs.
-
B.
federal oversight body
A federal oversight body is a government entity responsible for monitoring, evaluating, and enforcing compliance with laws, regulations, and standards across federal agencies or sectors to ensure accountability and integrity.
-
C.
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.
-
D.
proposed governmental body
A proposed governmental body is a conceptual organization suggested to perform specific public functions or governance roles, but which has not yet been formally established or granted legal authority.
-
E.
federal administrative unit
A federal administrative unit is a territorial or organizational subdivision within a federal state that carries out governmental functions and implements policies under the authority of the national government.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.