Triple
T28225123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cologne Bonn Airport |
E711564
|
entity |
| Predicate | hasLowCostCarrierTraffic |
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: [Cologne Bonn Airport, hasLowCostCarrierTraffic, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowCostCarrierTraffic Context triple: [Cologne Bonn Airport, hasLowCostCarrierTraffic, 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.
isLowCost
Indicates that something requires relatively little expenditure of money or resources compared to alternatives.
-
D.
lowCostTerminal
Indicates that the terminal operates or is provided at a relatively low financial cost compared to alternatives.
-
E.
hasNoRegularCommercialAirlineService
Indicates that a location or facility is not served by any scheduled, routine commercial airline flights.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 27, 2026, 10:49 p.m.