Triple
T3300566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Economy Class |
E69319
|
entity |
| Predicate | ticketFlexibilityComparedToPremiumCabins |
P9549
|
FINISHED |
| Object | lower |
—
|
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: lower | Statement: [Economy Class, ticketFlexibilityComparedToPremiumCabins, lower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketFlexibilityComparedToPremiumCabins Context triple: [Economy Class, ticketFlexibilityComparedToPremiumCabins, lower]
-
A.
serviceLevelComparedToEconomy
Indicates how the level or quality of service compares relative to an economy (baseline) service level.
-
B.
hasCabinClass
Indicates that an entity (such as a booking, ticket, or seat) is associated with a specific cabin class (e.g., economy, business, first).
-
C.
fareFlexibility
chosen
Indicates how easily a fare can be changed, canceled, or refunded, and under what conditions or penalties.
-
D.
ticketClass
Indicates the category or level of service assigned to a ticket within a ticketing or reservation system.
-
E.
comparedToOtherFares
Indicates a comparison relationship between one fare and other available fares, typically in terms of price, conditions, or benefits.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a66fcc819093931fe7a6507723 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.