Triple
T21703678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Euro 1968 matches |
E535718
|
entity |
| Predicate | usesTieBreakMethod |
P141055
|
FINISHED |
| Object | replay for drawn final |
—
|
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: replay for drawn final | Statement: [UEFA Euro 1968 matches, usesTieBreakMethod, replay for drawn final]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTieBreakMethod Context triple: [UEFA Euro 1968 matches, usesTieBreakMethod, replay for drawn final]
-
A.
useTiebreakers
chosen
Indicates that when primary criteria result in a tie, additional predefined rules or factors are applied to determine a winner or ordering.
-
B.
usesHeadToHeadAsTiebreaker
Indicates that a head-to-head comparison between entities is used to break a tie in their ranking or outcome.
-
C.
hasTieGame
Indicates that a game or match has ended with both sides having the same score, resulting in no winner.
-
D.
tiebreaker
Indicates that one entity serves as the deciding factor used to break a tie between two or more otherwise equal options or outcomes.
-
E.
pointsForTie
Indicates the number of points awarded to each side when a contest or game ends in a tie.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef9b82901c81909de242c920fbc164 |
completed | April 27, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:46 p.m.