Triple
T24515785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Euro 2016 Team of the Tournament |
E606364
|
entity |
| Predicate | hostTournamentFinalCity |
P34650
|
FINISHED |
| Object | Saint-Denis |
—
|
NE NERFINISHED |
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: Saint-Denis | Statement: [UEFA Euro 2016 Team of the Tournament, hostTournamentFinalCity, Saint-Denis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostTournamentFinalCity Context triple: [UEFA Euro 2016 Team of the Tournament, hostTournamentFinalCity, Saint-Denis]
-
A.
finalHostCity
chosen
Indicates the city that ultimately hosts or is selected to host a particular event or competition.
-
B.
lastHostCity
Indicates that one entity is the most recent city to have hosted the event or activity associated with the other entity.
-
C.
hostCityOfEvent
Indicates that a city serves as the location where a particular event is held or takes place.
-
D.
hostCityBidWinner
Indicates that a particular city has been selected as the winning bidder to host a specific event or competition.
-
E.
hostBidCity
Indicates that a city is serving or proposed to serve as the host location for a bid (e.g., for an event, project, or competition).
- 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_69e2c4c725148190a4e41577c5cb409c |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:24 a.m.