Triple
T4683478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillsborough Stadium |
E103859
|
entity |
| Predicate | HillsboroughDisasterDeaths |
P1785
|
FINISHED |
| Object | 97 |
—
|
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: 97 | Statement: [Hillsborough Stadium, HillsboroughDisasterDeaths, 97]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HillsboroughDisasterDeaths Context triple: [Hillsborough Stadium, HillsboroughDisasterDeaths, 97]
-
A.
numberOfSuspectedVictims
Indicates the count of individuals believed or alleged to be victims in a particular incident, case, or context.
-
B.
numberOfPeopleLaterDyingOfInjuriesConsidered
Indicates the number of people who subsequently died from injuries that were previously evaluated or taken into account.
-
C.
casualtiesAssociatedWithEvent
Indicates that certain casualties (deaths or injuries) are linked to, or resulted from, a specific event.
-
D.
numberOfPeoplePressedToDeath
Indicates the number of people who were killed specifically by being pressed to death.
-
E.
deathToll
chosen
Indicates the number of deaths resulting from a particular event, situation, or cause.
- 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.