Triple
T21693103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centre for Emergency Preparedness |
E535421
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency preparedness centre |
C37844
|
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 preparedness centre Context triple: [Centre for Emergency Preparedness, instanceOf, emergency preparedness centre]
-
A.
emergency management facility
chosen
An emergency management facility is a dedicated center where agencies coordinate, monitor, and direct resources and responses to emergencies and disasters.
-
B.
emergency preparedness program
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.
-
C.
emergency management agency
An emergency management agency is an organization responsible for preparing for, coordinating, and responding to natural or human-made disasters to protect people, property, and the environment.
-
D.
public health emergency coordination center
A public health emergency coordination center is a centralized facility that organizes, directs, and integrates multi-agency resources and information to prepare for, respond to, and recover from public health emergencies.
-
E.
emergency management training organization
An emergency management training organization designs and delivers specialized education, simulations, and certification programs to prepare individuals and agencies to effectively prevent, respond to, and recover from emergencies and disasters.
- 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_69e0c46a6ee481908836e1420fb78c9b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:45 p.m.