Triple
T7020870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA European Championship qualifying |
E162818
|
entity |
| Predicate | usesPlayOffs |
P2675
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [UEFA European Championship qualifying, usesPlayOffs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPlayOffs Context triple: [UEFA European Championship qualifying, usesPlayOffs, yes]
-
A.
hasPlayOffs
Indicates that a competition, league, or season includes a playoff stage to determine final rankings or a champion.
-
B.
hasPlayOffsFor
Indicates that an entity organizes or includes playoff competitions specifically for another entity (such as a league, season, or division).
-
C.
hasPlayoffsWith
Indicates that two entities participate together in the same playoff series, bracket, or postseason competition.
-
D.
usesPlayoffSeriesFormat
Indicates that a competition or league determines outcomes using a multi-game playoff series structure rather than single-elimination or standalone matches.
-
E.
usesPlayoffs
chosen
Indicates that a competition or league determines its final standings or champion through a postseason playoff format rather than solely by regular-season results.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b8118481909d76eb6616160e80 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:35 p.m.