Triple
T5525003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EGGW |
E144900
|
entity |
| Predicate | servesLowCostCarriers |
P60835
|
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: [EGGW, servesLowCostCarriers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesLowCostCarriers Context triple: [EGGW, servesLowCostCarriers, yes]
-
A.
hasLowCostCarrierFocus
Indicates that the subject is primarily oriented toward or strategically focused on serving low-cost carrier operations.
-
B.
hasLowCostCarrierOperations
chosen
Indicates that an entity operates or is served by low-cost (budget) airline services.
-
C.
lowCostTerminal
Indicates that the terminal operates or is provided at a relatively low financial cost compared to alternatives.
-
D.
servesAirline
Indicates that a transportation facility or location provides service for, or is regularly used by, a specified airline.
-
E.
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.
- 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_69c008f873a481909b4d9f7e2db3c37d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f874bd081909cccfc25767ee6fa |
completed | March 22, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69c01b0a06348190b39ac9fe80d2836a |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.