Triple
T14868766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Parade |
E349684
|
entity |
| Predicate | numberOfInjuredAt2010Disaster |
P63693
|
FINISHED |
| Object | over 500 |
—
|
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: over 500 | Statement: [Love Parade, numberOfInjuredAt2010Disaster, over 500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfInjuredAt2010Disaster Context triple: [Love Parade, numberOfInjuredAt2010Disaster, over 500]
-
A.
numberOfVictimsInjured
chosen
Indicates the count of victims who sustained injuries as a result of the event or incident.
-
B.
disasterDepicted
Indicates that one entity visually represents or portrays a disaster involving or affecting another entity.
-
C.
numberOfPeopleLaterDyingOfInjuriesConsidered
Indicates the number of people who subsequently died from injuries that were previously evaluated or taken into account.
-
D.
populationImpact2010Earthquake
Indicates the effect or consequences that the 2010 earthquake had on a population, such as changes in size, distribution, or demographic characteristics.
-
E.
numberOfVictimsConfirmed
Indicates the confirmed count of victims associated with an event, incident, or situation.
- F. None of above.
Provenance (3 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. |
Created at: April 10, 2026, 1:55 a.m.