Triple
T11467122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Euro 1988 matches |
E271806
|
entity |
| Predicate | tournamentStageIncluded |
P2703
|
FINISHED |
| Object | group stage |
—
|
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: group stage | Statement: [UEFA Euro 1988 matches, tournamentStageIncluded, group stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentStageIncluded Context triple: [UEFA Euro 1988 matches, tournamentStageIncluded, group stage]
-
A.
competitionStage
chosen
Indicates the specific phase or round within a broader competition in which the related entities participate or are situated.
-
B.
tournamentPhaseCoverage
Indicates the specific stage or phase of a tournament that an action, event, or data item pertains to or covers.
-
C.
divisionalRoundIncluded
Indicates that the referenced entity includes or pertains to the divisional round stage within a larger competition or playoff structure.
-
D.
finalTournamentStage
Indicates that an event or match represents the concluding or championship stage of a tournament.
-
E.
hasQuarterFinalStage
Indicates that a competition or event includes a quarter-final stage in its structure.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f5eb988190b309b8e309f6d1a5 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.