Triple
T22312854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Euro 1968 |
E551563
|
entity |
| Predicate | hasReplayFinalMatch |
P7495
|
FINISHED |
| Object | Italy vs Yugoslavia replay |
—
|
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: Italy vs Yugoslavia replay | Statement: [UEFA Euro 1968, hasReplayFinalMatch, Italy vs Yugoslavia replay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReplayFinalMatch Context triple: [UEFA Euro 1968, hasReplayFinalMatch, Italy vs Yugoslavia replay]
-
A.
hasFinalMatch
Indicates that an entity is associated with a concluding or decisive match in a series, tournament, or competition.
-
B.
hasReplay
Indicates that an event, action, or interaction is available to be viewed or experienced again in a recorded or reconstructed form.
-
C.
isRematchOfFinal
chosen
Indicates that a match is a subsequent encounter replaying the same opponents and stakes as a previous final match.
-
D.
isFinalPlayBy
Indicates that a particular play or move is the last one performed by a specified entity in a sequence or event.
-
E.
finalReplayWinner
Indicates that the referenced entity is the winner of a final match that was decided by a replay.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15750f76c81909d6f788928f503f1 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.