Triple
T28708595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WMO Environmental Emergency Response Programme |
E729765
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency response programme |
C22018
|
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: emergency response programme Context triple: [WMO Environmental Emergency Response Programme, instanceOf, emergency response programme]
-
A.
emergency preparedness program
chosen
An emergency preparedness program is a coordinated set of plans, training, resources, and procedures designed to help individuals, organizations, or communities effectively prevent, respond to, and recover from emergencies and disasters.
-
B.
emergency management framework
An emergency management framework is a structured approach that defines the processes, roles, resources, and coordination mechanisms needed to prepare for, respond to, recover from, and mitigate emergencies and disasters.
-
C.
emergency management document
An emergency management document is a formal record that outlines plans, procedures, roles, and resources for preparing for, responding to, and recovering from emergencies and disasters.
-
D.
emergency management facility
An emergency management facility is a dedicated center where agencies coordinate, monitor, and direct resources and responses to emergencies and disasters.
-
E.
temporary emergency program
A temporary emergency program is a short-term, rapidly implemented initiative designed to address urgent, unforeseen crises or critical needs until normal conditions or long-term solutions can be restored.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:46 a.m.