Triple
T16832384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Response Team |
E409182
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interagency committee |
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 committee Context triple: [National Response Team, instanceOf, interagency committee]
-
A.
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.
-
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.
intergovernmental working group
An intergovernmental working group is a collaborative body composed of representatives from multiple governments tasked with developing, coordinating, or advising on policies, standards, or actions in a specific issue area.
-
D.
interstate council
An interstate council is a formal collaborative body composed of representatives from multiple states or jurisdictions that coordinates policies, resolves shared issues, and facilitates joint decision-making across state boundaries.
-
E.
international committee
An international committee is a formally organized group of representatives from multiple countries who collaborate to discuss, coordinate, and make decisions on issues of shared global concern.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
Created at: April 10, 2026, 5:23 a.m.