Triple
T5494849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1968 UEFA European Championship |
E144185
|
entity |
| Predicate | decidingMatchType |
P30656
|
FINISHED |
| Object | 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: replay | Statement: [1968 UEFA European Championship, decidingMatchType, replay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidingMatchType Context triple: [1968 UEFA European Championship, decidingMatchType, replay]
-
A.
decidingMatchFor
Indicates a relationship where one entity is chosen or determined as the appropriate or final match for another entity among possible alternatives.
-
B.
finalMatchType
chosen
Indicates the specific category or format of the concluding or decisive match in a series or competition.
-
C.
matchType
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
D.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
E.
featuredMatchType
Indicates the specific category or kind of match that is highlighted or given special prominence.
- 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_69c008f5a2748190bce7a39aabf87a6d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f08c2a4819093e772a1497c7ecc |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b052f3c81909f71c6add0f35a6f |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:31 p.m.