Triple
T14171901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jolly Grant Airport |
E351228
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | VIDN |
E1075887
|
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: VIDN | Statement: [Jolly Grant Airport, ICAOcode, VIDN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VIDN Context triple: [Jolly Grant Airport, ICAOcode, VIDN]
-
A.
VIDN
VIDN is the four-letter ICAO airport code assigned to Noida International Airport in Uttar Pradesh, India.
-
B.
VIDN
chosen
VIDN is the ICAO airport code for Jolly Grant Airport serving Dehradun in the Indian state of Uttarakhand.
-
C.
VIDO
VIDO is a Canadian research organization at the University of Saskatchewan specializing in vaccine development and infectious disease research for both humans and animals.
-
D.
Vdio
Vdio was an online video-on-demand and streaming service launched by Skype and Rdio co-founder Janus Friis as an attempt to compete with platforms like Netflix.
-
E.
VIDP
VIDP is the ICAO airport code for Indira Gandhi International Airport, the primary international aviation hub serving New Delhi, 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b5dcbc8190b0cfcce5e6c6d582 |
completed | April 14, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcf808e6088190a607903be0f2adc7 |
completed | May 7, 2026, 8:37 p.m. |
Created at: April 10, 2026, 1:01 a.m.