Triple
T24318657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1902 Ibrox disaster |
E612894
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | human stampede and structural failure event |
C11630
|
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 stampede and structural failure event Context triple: [1902 Ibrox disaster, instanceOf, human stampede and structural failure event]
-
A.
human stampede
chosen
A human stampede is a chaotic, high-density crowd movement in which people, often driven by panic or urgency, push and surge in a confined space, leading to trampling, crushing, and potentially mass casualties.
-
B.
crowd crush
A crowd crush is a dangerous, often deadly situation in which a dense crowd becomes so tightly packed that people are unable to move or breathe, leading to compressive asphyxia and trampling.
-
C.
bridge collapse
A bridge collapse is the sudden structural failure of a bridge, causing partial or total loss of its load-bearing capacity and resulting in the deck or supporting elements falling or deforming beyond safe use.
-
D.
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.
-
E.
structural failure
Structural failure is the loss of a structure’s ability to safely carry intended loads due to material, design, construction, or degradation-related deficiencies.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 1:47 a.m.