Triple
T26229911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1986–87 European Cup |
E656005
|
entity |
| Predicate | cityOfFinalVenue |
P34650
|
FINISHED |
| Object | Vienna |
—
|
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: Vienna | Statement: [1986–87 European Cup, cityOfFinalVenue, Vienna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityOfFinalVenue Context triple: [1986–87 European Cup, cityOfFinalVenue, Vienna]
-
A.
cityOfVenue
Indicates the city in which a given venue is located.
-
B.
finalCity
Indicates that a given city is the last or ultimate city associated with an entity within a sequence, process, or journey.
-
C.
finalHostCity
chosen
Indicates the city that ultimately hosts or is selected to host a particular event or competition.
-
D.
firstFinalCity
Indicates that a city is the final destination reached first in some ordered sequence of trips or routes.
-
E.
finalConcertLocation
Indicates the location where a concert or performance ultimately takes place, especially after any changes or planning stages.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d56b0388190826b97fa17dc97ce |
completed | May 2, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:59 p.m.