Triple
T11885017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 11/29 |
E282756
|
entity |
| Predicate | IATAAirportCode |
P418
|
FINISHED |
| Object | VOG |
E229868
|
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: VOG | Statement: [Runway 11/29, IATAAirportCode, VOG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VOG Context triple: [Runway 11/29, IATAAirportCode, VOG]
-
A.
VOG
chosen
VOG is the IATA airport code for Volgograd International Airport, a regional air transport hub serving the city of Volgograd in Russia.
-
B.
VOGA
VOGA is the ICAO airport code assigned to Manohar International Airport in Mopa, Goa, India.
-
C.
VOH
VOH is the vehicle registration code used on license plates for the district of Neustadt an der Waldnaab in Bavaria, Germany.
-
D.
VOZ
VOZ is the IATA airport code for Voronezh Peter the Great Airport in Voronezh, Russia.
-
E.
VOZ
VOZ is the ICAO airline designator used to identify Virgin Australia in international aviation operations.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a02ad4819090faef0e0be732ee |
completed | April 10, 2026, 10:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f281f488a8819082f40dfdd12f29a2 |
completed | April 29, 2026, 10:11 p.m. |
Created at: April 8, 2026, 9:44 p.m.