Triple
T5678128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire and Disaster Management Agency |
E125135
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | disaster management authority |
C5073
|
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: disaster management authority Context triple: [Fire and Disaster Management Agency, instanceOf, disaster management authority]
-
A.
disaster management initiative
A disaster management initiative is a coordinated program or effort designed to prevent, prepare for, respond to, and recover from natural or human-made disasters to protect lives, property, and the environment.
-
B.
emergency management agency
chosen
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.
-
C.
civil affairs unit
A civil affairs unit is a military organization responsible for managing relationships and coordination between armed forces and civilian populations, authorities, and institutions in areas of operation.
-
D.
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.
-
E.
disaster
A disaster is a sudden, disruptive event—natural or human-made—that causes significant harm to people, property, or the environment and overwhelms normal coping capacities.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:43 p.m.