Triple
T777334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 6 |
E16416
|
entity |
| Predicate | servesFlightType |
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: [Terminal 6, servesFlightType, domestic flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesFlightType Context triple: [Terminal 6, servesFlightType, 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.
hasTypeOfFlights
chosen
Indicates that an entity offers, includes, or is associated with specific categories or kinds of flights.
-
C.
servesAirline
Indicates that a transportation facility or location provides service for, or is regularly used by, a specified airline.
-
D.
servesAirport
Indicates that a transportation service or route provides access to and operates for a particular airport.
-
E.
airlineType
Indicates the classification or category of an airline based on its operational or service characteristics.
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a74da7648190adfad56717d564df |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a50a443481909ae3662764ee69a4 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.