Triple
T8773620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cochin International Airport |
E208522
|
entity |
| Predicate | hasAirportCode |
P6089
|
FINISHED |
| Object | VOCI |
E757694
|
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: VOCI | Statement: [Cochin International Airport, hasAirportCode, VOCI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VOCI Context triple: [Cochin International Airport, hasAirportCode, VOCI]
-
A.
VOCI
chosen
VOCI is the ICAO airport code for Cochin International Airport in Kochi, India, a major international gateway in the state of Kerala.
-
B.
VOZ
VOZ is the IATA airport code for Voronezh Peter the Great Airport in Voronezh, Russia.
-
C.
VOZ
VOZ is the ICAO airline designator used to identify Virgin Australia in international aviation operations.
-
D.
voco
voco is a contemporary upscale hotel brand within the InterContinental Hotels Group portfolio, known for its relaxed style and locally inspired guest experiences.
-
E.
VOI
VOI is the ICAO airline designator used to identify Volaris, a Mexican low-cost carrier, in aviation operations and communications.
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f2dc87c8190be0597a260d95a0b |
completed | March 31, 2026, 11:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf6f2793688190a23ab55eba95e177 |
completed | April 3, 2026, 7:41 a.m. |
Created at: March 30, 2026, 6:41 p.m.