Triple
T28480101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union civil protection mechanisms |
E720668
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | disaster risk management mechanism |
C11471
|
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 risk management mechanism Context triple: [European Union civil protection mechanisms, instanceOf, disaster risk management mechanism]
-
A.
disaster management initiative
chosen
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.
disaster management law
Disaster management law is the body of legal rules, principles, and procedures that governs how governments and organizations prepare for, respond to, recover from, and mitigate natural or human-made disasters while protecting public safety and rights.
-
C.
resilience management framework
A resilience management framework is a structured approach that integrates policies, processes, and tools to anticipate, absorb, adapt to, and recover from disruptions while maintaining essential functions and enabling continuous improvement.
-
D.
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.
-
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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 2:54 a.m.