Triple
T22874784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croatia vs Scotland (UEFA Euro 2020 Group D) |
E567293
|
entity |
| Predicate | ScotlandGroupPositionAfterMatch |
P150073
|
FINISHED |
| Object | fourth in Group D |
—
|
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: fourth in Group D | Statement: [Croatia vs Scotland (UEFA Euro 2020 Group D), ScotlandGroupPositionAfterMatch, fourth in Group D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ScotlandGroupPositionAfterMatch Context triple: [Croatia vs Scotland (UEFA Euro 2020 Group D), ScotlandGroupPositionAfterMatch, fourth in Group D]
-
A.
leagueCupResult
Indicates the outcome or standing a team or participant achieved in a specific league cup competition.
-
B.
ShrovetideFootballTeams
Indicates that the related entities are opposing teams participating in a Shrovetide football match.
-
C.
ScottishCupTitles
Indicates the number of times an entity has won the Scottish Cup football competition.
-
D.
leagueDraws
Indicates that a league competition or season resulted in a specified number of drawn (tied) matches.
-
E.
wonScottishCup
Indicates that the subject achieved victory in the Scottish Cup competition.
- F. None of above. chosen
Provenance (4 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f57a1ec8190b8c6a0080d97a2a2 |
completed | April 29, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69eed2d8c0608190afef4c4e530c0e2c |
completed | April 27, 2026, 3:07 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:39 p.m.