Triple
T14868767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Parade |
E349684
|
entity |
| Predicate | consequenceOf2010Disaster |
P115941
|
FINISHED |
| Object | permanent discontinuation of the festival |
—
|
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: permanent discontinuation of the festival | Statement: [Love Parade, consequenceOf2010Disaster, permanent discontinuation of the festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOf2010Disaster Context triple: [Love Parade, consequenceOf2010Disaster, permanent discontinuation of the festival]
-
A.
disasterDepicted
Indicates that one entity visually represents or portrays a disaster involving or affecting another entity.
-
B.
causeOfDisaster
Indicates that the subject is responsible for bringing about or triggering the specified disaster.
-
C.
consequenceOfDestruction
Indicates that one event, state, or condition occurs as a direct result of a prior act of destruction.
-
D.
floodConsequence
Indicates the resulting effects, outcomes, or impacts that occur as a consequence of a flood event.
-
E.
hasDisaster
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5776b848190bfe3a06ff261dc31 |
completed | April 15, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:55 a.m.