Triple
T1493561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Super Cup |
E29635
|
entity |
| Predicate | deciderIfDraw |
P27778
|
FINISHED |
| Object | extra time |
—
|
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: extra time | Statement: [UEFA Super Cup, deciderIfDraw, extra time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deciderIfDraw Context triple: [UEFA Super Cup, deciderIfDraw, extra time]
-
A.
decidingMethodForDrawnFinals
chosen
Indicates the method or procedure used to determine the outcome or winner when a final match or contest ends in a draw.
-
B.
decidingGameWinner
Indicates that an event, action, or process determines which participant is the winner of a game.
-
C.
numberOfDraws
Indicates the total count of times an event, game, or contest has ended in a draw or tie.
-
D.
decidedWith
Indicates that an entity made a decision jointly or in agreement with another entity.
-
E.
decidingMatchFor
Indicates a relationship where one entity is chosen or determined as the appropriate or final match for another entity among possible alternatives.
- 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6c665488190ae665f7a1b0563f5 |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c48902808190a8028d359bcf123e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.