Triple
T18749389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kochi International Airport |
E458486
|
entity |
| Predicate | servesFlightTypes |
P18239
|
FINISHED |
| Object | domestic flights |
—
|
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: domestic flights | Statement: [Kochi International Airport, servesFlightTypes, domestic flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesFlightTypes Context triple: [Kochi International Airport, servesFlightTypes, domestic flights]
-
A.
servesAirlineType
Indicates that a service provider (such as an airport, terminal, or facility) accommodates or operates flights for a specified type or category of airline.
-
B.
servesAviationType
Indicates that one entity provides services or functions specifically for a particular type or category of aviation.
-
C.
hasTypeOfFlights
chosen
Indicates that an entity offers, includes, or is associated with specific categories or kinds of flights.
-
D.
servesAirportType
Indicates that a transportation service or facility provides service to, or is designated for, a specific type or category of airport.
-
E.
servesFlightsTo
Indicates that one transportation provider regularly operates flights to a specified destination location.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579eb7350819099d7291207781116 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.