Triple
T23688516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 Cumbria floods |
E585232
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | disaster in 2009 |
C223
|
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 in 2009 Context triple: [2009 Cumbria floods, instanceOf, disaster in 2009]
-
A.
disaster
chosen
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.
-
B.
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.
-
C.
disaster in British India
A disaster in British India is a catastrophic event—natural or man-made—that occurred during the period of British colonial rule in the Indian subcontinent, causing widespread loss of life, property, or social disruption.
-
D.
sports-related disaster
A sports-related disaster is a catastrophic event occurring in connection with a sporting activity or venue—such as during games, training, or associated travel—that results in significant injury, loss of life, or large-scale harm to people or property.
-
E.
crisis
A crisis is a critical turning point or period of intense difficulty and instability that demands urgent decision-making and action to prevent severe negative consequences.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:52 p.m.