Triple
T26818877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Columbia Hazard Mitigation Plan |
E675192
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hazard mitigation plan |
C20646
|
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: hazard mitigation plan Context triple: [District of Columbia Hazard Mitigation Plan, instanceOf, hazard mitigation plan]
-
A.
state emergency management plan
chosen
A state emergency management plan is a comprehensive, government-developed framework that outlines policies, roles, resources, and coordinated procedures for preventing, preparing for, responding to, and recovering from disasters and emergencies within a state’s jurisdiction.
-
B.
geohazards risk reduction program
A geohazards risk reduction program is a coordinated set of policies, practices, and interventions designed to identify, assess, and mitigate risks from geological hazards such as earthquakes, landslides, and volcanic eruptions to protect people, infrastructure, and the environment.
-
C.
flood risk reduction program
A flood risk reduction program is an organized set of policies, projects, and practices designed to lessen the likelihood and impacts of flooding on people, property, and the environment.
-
D.
preparedness planning tool
A preparedness planning tool is a system that helps individuals or organizations assess risks, organize resources, and create actionable plans to effectively respond to and recover from emergencies or disruptions.
-
E.
flood hazard map
A flood hazard map is a spatial representation that delineates areas at varying risk of flooding based on factors such as historical events, topography, hydrology, and projected climate or land-use changes.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 4:54 a.m.