Triple
T22727687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arena Lviv |
E562040
|
entity |
| Predicate | cityForTournament |
P19642
|
FINISHED |
| Object | Lviv UEFA Euro 2012 host city |
—
|
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: Lviv UEFA Euro 2012 host city | Statement: [Arena Lviv, cityForTournament, Lviv UEFA Euro 2012 host city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityForTournament Context triple: [Arena Lviv, cityForTournament, Lviv UEFA Euro 2012 host city]
-
A.
hostCityOfEvent
Indicates that a city serves as the location where a particular event is held or takes place.
-
B.
bubbleTournamentCity
Indicates that a tournament is held in a specific city within a controlled or "bubble" environment.
-
C.
cityOfVenue
chosen
Indicates the city in which a given venue is located.
-
D.
sponsorCity
Indicates that an entity provides sponsorship or financial support to a particular city.
-
E.
hostCitySelection
Indicates the selection of a particular city to serve as the official host location for an event or activity.
- 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1792b22cc819099aa00bb2dbacce3 |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:21 p.m.