Triple
T16529158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lohegaon Air Force Station |
E401517
|
entity |
| Predicate | ICAOCode |
P419
|
FINISHED |
| Object | VAPO |
E401516
|
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: VAPO | Statement: [Lohegaon Air Force Station, ICAOCode, VAPO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VAPO Context triple: [Lohegaon Air Force Station, ICAOCode, VAPO]
-
A.
VAPO
chosen
VAPO is the ICAO airport code for Pune International Airport, a major civil and military air hub serving the city of Pune in Maharashtra, India.
-
B.
Vapors
"Vapors" is a song by American singer Jhené Aiko featured on her debut EP "Sail Out."
-
C.
VAP
VAP is the railway station code used to identify Beijing North railway station in China’s rail network.
-
D.
Vuse
Vuse is an electronic cigarette and vaping product brand owned by British American Tobacco, known for its range of nicotine e-liquids and devices.
-
E.
VOG
VOG is the IATA airport code for Volgograd International Airport, a regional air transport hub serving the city of Volgograd in Russia.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed625208190a68b879266b05b3f |
completed | April 18, 2026, 7:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0067a913388190afebe40fcc42e731 |
completed | May 10, 2026, 11:10 a.m. |
Created at: April 10, 2026, 5:14 a.m.