Triple
T4882150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porbandar Airport |
E109352
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | VAPR |
E109352
|
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: VAPR | Statement: [Porbandar Airport, ICAO code, VAPR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VAPR Context triple: [Porbandar Airport, ICAO code, VAPR]
-
A.
VAPR
chosen
VAPR is the ICAO airport code assigned to Porbandar Airport in Gujarat, India.
-
B.
VABP
VABP is the ICAO airport code for Raja Bhoj Airport, the primary airport serving Bhopal in the Indian state of Madhya Pradesh.
-
C.
VANP
VANP is the ICAO airport code for Dr. Babasaheb Ambedkar International Airport in Nagpur, India.
-
D.
VAB
VAB is the commonly used abbreviation for NASA’s Vehicle Assembly Building, the massive structure at Kennedy Space Center where rockets are assembled before launch.
-
E.
VAPO
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.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6dde6fcc8190a5aa7587f85632bd |
completed | March 20, 2026, 3:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be68070bb0819095bda199cc966d31 |
completed | March 21, 2026, 9:42 a.m. |
Created at: March 20, 2026, 1:27 p.m.