Triple
T2274744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puebla International Airport |
E50743
|
entity |
| Predicate | handlesFlightType |
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: [Puebla International Airport, handlesFlightType, domestic flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesFlightType Context triple: [Puebla International Airport, handlesFlightType, domestic flights]
-
A.
hasTypeOfFlights
chosen
Indicates that an entity offers, includes, or is associated with specific categories or kinds of flights.
-
B.
flightRegime
Indicates the operational conditions or phase of flight under which an aircraft or aerospace vehicle is functioning (e.g., speed, altitude, and atmospheric regime).
-
C.
airlineType
Indicates the classification or category of an airline based on its operational or service characteristics.
-
D.
servesPassengerTrafficType
Indicates that a transportation facility or service accommodates a specified type or category of passenger traffic.
-
E.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
- 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_69a88b05910c8190a9a2b1ff230c85f9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc39c6ff0819081a07696f1c29990 |
completed | March 7, 2026, 6:20 a.m. |
| PD | Predicate disambiguation | batch_69abbdb7719081909143efa8f48df4e4 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.