Triple
T13591899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LKO |
E324710
|
entity |
| Predicate | hasTerminal |
P182
|
FINISHED |
| Object |
Terminal 1
Terminal 1 is a passenger terminal at Lucknow’s Chaudhary Charan Singh International Airport (IATA: LKO) in India.
|
E325960
|
NE FINISHED |
How this triple was built (4 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: Terminal 1 | Statement: [LKO, hasTerminal, Terminal 1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Terminal 1 Context triple: [LKO, hasTerminal, Terminal 1]
-
A.
Terminal 1
Terminal 1 is one of the main passenger terminals at Paris Charles de Gaulle Airport, known for its distinctive circular design and central location within the airport complex.
-
B.
Terminal 1
Terminal 1 is the main passenger terminal at El Dorado International Airport in Bogotá, Colombia, handling the majority of the airport’s domestic and international flights.
-
C.
Terminal 1
Terminal 1 is the main passenger terminal at Brussels South Charleroi Airport, handling the majority of the airport’s commercial flights and traveler services.
-
D.
Terminal 1
Terminal 1 is the main passenger terminal at Milan Malpensa Airport, handling the bulk of its international and domestic flights with extensive services and facilities.
-
E.
Terminal 1
Terminal 1 is a domestic passenger terminal at Sardar Vallabhbhai Patel International Airport in Ahmedabad, India.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Terminal 1 Triple: [LKO, hasTerminal, Terminal 1]
Generated description
Terminal 1 is a passenger terminal at Lucknow’s Chaudhary Charan Singh International Airport (IATA: LKO) in India.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Terminal 1 Target entity description: Terminal 1 is a passenger terminal at Lucknow’s Chaudhary Charan Singh International Airport (IATA: LKO) in India.
-
A.
Terminal 1
chosen
Terminal 1 is a passenger terminal at Chaudhary Charan Singh International Airport in Lucknow, India, serving as one of the airport’s main facilities for handling air travelers.
-
B.
Terminal 1
Terminal 1 is a domestic flight terminal at Indira Gandhi International Airport in Delhi, primarily serving low-cost and short-haul carriers.
-
C.
Terminal 1
Terminal 1 is a major passenger terminal at Kempegowda International Airport in Bengaluru, handling a large share of the airport’s domestic and international flights.
-
D.
Terminal 1
Terminal 1 is a domestic passenger terminal at Chhatrapati Shivaji Maharaj International Airport in Mumbai, India.
-
E.
Terminal 1
Terminal 1 is a domestic passenger terminal at Sardar Vallabhbhai Patel International Airport in Ahmedabad, India.
- F. None of above.
Provenance (5 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb056ce088190a6feb4266633d18b |
completed | April 12, 2026, 2:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76bc578908190abd5cca94b1c3a5c |
completed | May 3, 2026, 3:37 p.m. |
| NEDg | Description generation | batch_69f77643b0348190962bf23a9857edbe |
completed | May 3, 2026, 4:22 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f7792110e48190a29b6e89c6ebcc03 |
completed | May 3, 2026, 4:34 p.m. |
Created at: April 9, 2026, 9:49 p.m.