Triple
T2625315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heysel Stadium disaster |
E59103
|
entity |
| Predicate | sanctionTarget |
P39509
|
FINISHED |
| Object | English football clubs |
—
|
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: English football clubs | Statement: [Heysel Stadium disaster, sanctionTarget, English football clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanctionTarget Context triple: [Heysel Stadium disaster, sanctionTarget, English football clubs]
-
A.
sanction
chosen
Indicates the imposition of an official penalty or restrictive measure by an authority in response to certain actions or behaviors.
-
B.
typeOfSanction
Indicates the specific category or kind of sanction that is applied in a given situation.
-
C.
canImposeSanctions
Indicates that one entity has the authority or power to apply punitive or restrictive measures (sanctions) against another entity.
-
D.
receivedSanctionFrom
Indicates that one entity has been subjected to a formal penalty, restriction, or disciplinary measure imposed by another entity.
-
E.
requiresSanctioningBody
Indicates that an action, event, or decision must be approved or authorized by a designated sanctioning authority or governing body.
- 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_69ab4ac558388190962492cd2e1b0ce6 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdb0e7b888190bfa5d2e33f00ec0f |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd810d7f481908e81c305772c4c14 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.