Triple
T7302812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EURO |
E167898
|
entity |
| Predicate | previousFinalTournamentTeams |
P65054
|
FINISHED |
| Object | 16 |
—
|
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: 16 | Statement: [EURO, previousFinalTournamentTeams, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousFinalTournamentTeams Context triple: [EURO, previousFinalTournamentTeams, 16]
-
A.
finalTeam
Indicates that an entity is the ultimate or concluding team associated with another entity or process.
-
B.
finalsTeam
Indicates that a team has qualified for and is participating in the final round or championship stage of a competition.
-
C.
numberOfFinalTournamentTeams
chosen
Indicates the total count of teams that participate in the final stage of a tournament.
-
D.
finalTournamentParticipants
Indicates that the specified entities are the participants who qualified for and compete in the final round of a tournament.
-
E.
previousFinals
Indicates that one entity represents a past or prior finals event or appearance in relation to another entity.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebb2261c8190ae9095c8e110b528 |
completed | March 27, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.