Triple
T25635193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pukkelpop |
E642678
|
entity |
| Predicate | 2011StageCollapse |
P158942
|
FINISHED |
| Object | caused multiple fatalities and injuries |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: caused multiple fatalities and injuries | Statement: [Pukkelpop, 2011StageCollapse, caused multiple fatalities and injuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2011StageCollapse Context triple: [Pukkelpop, 2011StageCollapse, caused multiple fatalities and injuries]
-
A.
towerCollapsedIn
Indicates that a tower underwent structural failure and collapsed at or within a specified location or context.
-
B.
causedBuildingCollapse
Indicates that one entity was responsible for bringing about the structural failure or collapse of a building.
-
C.
roofCollapsed
Indicates that the roof of a structure has given way or fallen in, typically due to structural failure or external forces.
-
D.
collapseType
Indicates the specific manner or category of failure by which something collapses or structurally gives way.
-
E.
ceilingCollapseFatalities
Indicates that a ceiling collapse event resulted in one or more fatalities.
- F. None of above. chosen
Provenance (4 batches)
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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa60db0c8190b5c615e6dc35264a |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 5:21 p.m.