Triple
T14868764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Parade |
E349684
|
entity |
| Predicate | 2010DuisburgEvent |
P115940
|
FINISHED |
| Object | crowd disaster with multiple fatalities |
—
|
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: crowd disaster with multiple fatalities | Statement: [Love Parade, 2010DuisburgEvent, crowd disaster with multiple fatalities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2010DuisburgEvent Context triple: [Love Parade, 2010DuisburgEvent, crowd disaster with multiple fatalities]
-
A.
eventEdition
Indicates a specific version or iteration of an event within a recurring or multi-edition series.
-
B.
organisedDuring
Indicates that an organizing action or arrangement took place within the time span of a specified event or period.
-
C.
BaselShowHeldAt
Indicates that a specific edition of the Basel art show is held at a particular venue or location.
-
D.
competitionDepicted
Indicates that a competitive event or rivalry between entities is shown or represented in some medium or context.
-
E.
wasEuropeanCapitalOfCultureInYear
Indicates that a city held the official title of European Capital of Culture in the specified year.
- 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.