Triple
T2625316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heysel Stadium disaster |
E59103
|
entity |
| Predicate | banDurationApproximate |
P42310
|
FINISHED |
| Object | 5 years |
—
|
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: 5 years | Statement: [Heysel Stadium disaster, banDurationApproximate, 5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: banDurationApproximate Context triple: [Heysel Stadium disaster, banDurationApproximate, 5 years]
-
A.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
B.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
C.
possibleDuration
Indicates the range or specific length of time that an action, event, or state can last or is allowed to last.
-
D.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
E.
sessionLength
Indicates the duration of time that a particular session lasts from start to end.
- 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_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. |
| PDg | Predicate description generation | batch_69abdb0bf9b881908b239c1310c7bbf3 |
completed | March 7, 2026, 8 a.m. |
Created at: March 6, 2026, 9:50 p.m.