Triple
T4208408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premium Economy |
E93837
|
entity |
| Predicate | offersMoreComfortThan |
P9054
|
FINISHED |
| Object | Economy Class |
—
|
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: Economy Class | Statement: [Premium Economy, offersMoreComfortThan, Economy Class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersMoreComfortThan Context triple: [Premium Economy, offersMoreComfortThan, Economy Class]
-
A.
designedForComfort
Indicates that something has been intentionally created or configured to enhance physical or psychological ease and reduce discomfort.
-
B.
relativeComfort
chosen
Indicates a comparative relationship where one entity is judged to be more or less comfortable than another under given conditions.
-
C.
offersFeature
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
D.
comfortLevelComparedToPremiumCabins
Indicates how the comfort level of something compares relative to that of premium cabins.
-
E.
hasTopFloorFeature
Indicates that a building’s top floor possesses a specific feature, attribute, or amenity.
- 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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:03 p.m.