Triple
T3111659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lal Bahadur Shastri International Airport |
E64964
|
entity |
| Predicate | offersDomesticFlights |
P1658
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [Lal Bahadur Shastri International Airport, offersDomesticFlights, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersDomesticFlights Context triple: [Lal Bahadur Shastri International Airport, offersDomesticFlights, yes]
-
A.
hasDomesticFlights
chosen
Indicates that an airline or airport operates flights within the same country, connecting domestic destinations.
-
B.
operatesFlightsTo
Indicates that one entity (typically an airline) runs or provides flight services to the location represented by the other entity.
-
C.
hasTypeOfFlights
Indicates that an entity offers, includes, or is associated with specific categories or kinds of flights.
-
D.
hasScheduledFlights
Indicates that there are one or more flights planned and set to occur between the related entities according to a schedule.
-
E.
numberOfFlights
Indicates the total count of flights associated with a given entity or within a specified context.
- F. None of above.
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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada43954f0819096a96331bf3c53a8 |
completed | March 8, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.