Triple
T27679870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Yellowstone Coordinating Committee |
E697877
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interagency coordinating body |
C37895
|
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: interagency coordinating body Context triple: [Greater Yellowstone Coordinating Committee, instanceOf, interagency coordinating body]
-
A.
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.
-
B.
interagency committee
chosen
An interagency committee is a collaborative body composed of representatives from multiple government agencies formed to coordinate policies, share information, and address cross-cutting issues.
-
C.
interagency coordination arrangement
An interagency coordination arrangement is a structured agreement or framework that defines how multiple government or organizational agencies collaborate, share information, and align responsibilities to achieve common objectives.
-
D.
interagency group
An interagency group is a collaborative body composed of representatives from multiple government agencies that coordinates policies, resources, and actions on shared issues or objectives.
-
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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:46 p.m.