Triple
T36197755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNNM |
E1047174
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inter-agency network |
C33223
|
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: inter-agency network Context triple: [UNNM, instanceOf, inter-agency network]
-
A.
inter-agency coordination network
chosen
An inter-agency coordination network is a structured system of relationships, processes, and communication channels that enables multiple organizations or agencies to collaboratively plan, share information, and align actions toward common objectives.
-
B.
intergovernmental coordination network
An intergovernmental coordination network is a structured system of relationships, processes, and communication channels that enables multiple governmental entities at different levels or jurisdictions to align policies, share information, and collaborate on common objectives.
-
C.
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.
-
D.
interagency committee
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.
-
E.
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.
- 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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.