Triple
T2464257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta One |
E55205
|
entity |
| Predicate | serviceLevelComparedToEconomy |
P40004
|
FINISHED |
| Object | higher |
—
|
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: higher | Statement: [Delta One, serviceLevelComparedToEconomy, higher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceLevelComparedToEconomy Context triple: [Delta One, serviceLevelComparedToEconomy, higher]
-
A.
offersEconomyClass
Indicates that an entity provides or makes available an economy-class option within its services or offerings.
-
B.
comparedToOtherFares
Indicates a comparison relationship between one fare and other available fares, typically in terms of price, conditions, or benefits.
-
C.
airlineScale
Indicates that one airline is a subsidiary, regional brand, or otherwise operates at a smaller or supporting scale relative to another airline.
-
D.
serviceLevel
Indicates the degree or quality of service provided or received in the relationship between entities.
-
E.
hasCabinClass
Indicates that an entity (such as a booking, ticket, or seat) is associated with a specific cabin class (e.g., economy, business, first).
- F. None of above. chosen
Provenance (4 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_69ab49e3622c8190ad22afa2c4fbb807 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0b3ea308190a6d8499c2a542c50 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd2baee308190bdaa41ef1f6bc9cc |
completed | March 7, 2026, 7:24 a.m. |
Created at: March 6, 2026, 9:44 p.m.