Triple
T35468832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teton Dam failure flooding |
E1025153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | human-caused disaster |
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: human-caused disaster Context triple: [Teton Dam failure flooding, instanceOf, human-caused disaster]
-
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.
humanitarian emergency
A humanitarian emergency is a crisis situation, often caused by conflict, disaster, or epidemic, that overwhelms local capacity and threatens large numbers of people’s lives, health, or basic well-being, requiring urgent international assistance.
-
C.
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.
-
D.
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.
-
E.
prison disaster
A prison disaster is a catastrophic event occurring within a correctional facility—such as a fire, riot, structural collapse, epidemic, or mass escape—that results in significant harm, disruption, or loss of life among inmates, staff, or surrounding communities.
- 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.