Triple
T26818880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Columbia Hazard Mitigation Plan |
E675192
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency management document |
C52075
|
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 management document Context triple: [District of Columbia Hazard Mitigation Plan, instanceOf, emergency management document]
-
A.
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.
-
B.
emergency management domain
The emergency management domain encompasses the coordinated processes, roles, technologies, and policies used to prepare for, respond to, recover from, and mitigate the impacts of disasters and crises.
-
C.
emergency management concept
An emergency management concept is a foundational idea, principle, or framework that guides how communities, organizations, and agencies prepare for, respond to, recover from, and mitigate the impacts of disasters and crises.
-
D.
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.
-
E.
emergency management role
An emergency management role is responsible for planning, coordinating, and directing resources and actions before, during, and after emergencies or disasters to protect people, property, and the environment.
- F. None of above. chosen
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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 4:54 a.m.