Triple
T10780567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INS Hansa |
E254307
|
entity |
| Predicate | hasIcaoCode |
P419
|
FINISHED |
| Object | VOGO |
E254306
|
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: VOGO | Statement: [INS Hansa, hasIcaoCode, VOGO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VOGO Context triple: [INS Hansa, hasIcaoCode, VOGO]
-
A.
VOGO
chosen
VOGO is the ICAO airport code assigned to Dabolim Airport, the main international airport serving the state of Goa, India.
-
B.
VOG
VOG is the IATA airport code for Volgograd International Airport, a regional air transport hub serving the city of Volgograd in Russia.
-
C.
VEHO
VEHO is the ICAO airport code assigned to Donyi Polo Airport in Arunachal Pradesh, India.
-
D.
VOI
VOI is the ICAO airline designator used to identify Volaris, a Mexican low-cost carrier, in aviation operations and communications.
-
E.
VAOZ
VAOZ is the ICAO airport code assigned to Nashik Airport in Maharashtra, 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732c384bc81908f503f3a2e0503a4 |
completed | April 9, 2026, 5:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de55fbfc70819098eb40cf0d1b9e8c |
completed | April 14, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:17 p.m.