Triple
T34403921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IERS Central Bureau |
E883056
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coordinating bureau |
C14661
|
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: coordinating bureau Context triple: [IERS Central Bureau, instanceOf, coordinating bureau]
-
A.
coordination office
chosen
A coordination office is an organizational unit responsible for planning, aligning, and overseeing activities, resources, and communication among different stakeholders to ensure smooth and efficient execution of projects or operations.
-
B.
intergovernmental coordination agency
An intergovernmental coordination agency is an organization formed by multiple governments to align policies, share information, and manage joint initiatives across jurisdictions.
-
C.
bureau-level office
A bureau-level office is an organizational unit within a larger department or agency that operates at the bureau tier, managing specialized programs, policies, or services under that bureau’s authority.
-
D.
Economic Coordination Committee of the Cabinet
The Economic Coordination Committee of the Cabinet is a high-level governmental body responsible for formulating, coordinating, and approving key economic and financial policies and decisions on behalf of the federal cabinet.
-
E.
intelligence coordination body
An intelligence coordination body is an organization responsible for integrating, harmonizing, and directing the activities, information sharing, and strategic priorities of multiple intelligence agencies or units to support national or organizational security 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:59 a.m.