Triple
T11647187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna International Airport |
E276805
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | VIE |
E276804
|
NE 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: VIE | Statement: [Vienna International Airport, IATACode, VIE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VIE Context triple: [Vienna International Airport, IATACode, VIE]
-
A.
VIE
chosen
VIE is the three-letter IATA airport code for Vienna International Airport, the main international gateway to Vienna, Austria.
-
B.
VIE
VIE is the stock ticker symbol for Veolia Environnement, a French multinational company specializing in water, waste, and energy management services.
-
C.
VIAM
VIAM is the ICAO airport code for Ambala Air Force Station, a major Indian Air Force base located in Ambala, Haryana, India.
-
D.
VIV
VIV is the ICAO airline designator assigned to Viva Aerobus, a Mexican low-cost carrier.
-
E.
VIBN
VIBN is the ICAO airport code for Lal Bahadur Shastri International Airport serving Varanasi, India.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cd9bb0819093d107204bed2fe0 |
completed | April 10, 2026, 7:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ee87f903c48190b9055ad4cfebb1e1 |
completed | April 26, 2026, 9:47 p.m. |
Created at: April 8, 2026, 9:39 p.m.