Triple
T32158112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Disaster Risk Reduction and Management Council |
E821352
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inter-agency council |
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: inter-agency council Context triple: [National Disaster Risk Reduction and Management Council, instanceOf, inter-agency council]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
intergovernmental board
An intergovernmental board is a formal decision-making body composed of representatives from multiple governments that coordinates policies, oversees joint initiatives, and manages shared responsibilities across participating states.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:32 a.m.