Triple
T7357685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Residence (on selected A380 aircraft) |
E169666
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ultra-luxury first-class airline suite |
C3322
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ultra-luxury first-class airline suite Context triple: [The Residence (on selected A380 aircraft), instanceOf, ultra-luxury first-class airline suite]
-
A.
premium airport lounge
A premium airport lounge is an exclusive, comfortable space within an airport offering enhanced services such as seating, food and beverages, Wi‑Fi, and other amenities to eligible travelers seeking a quieter, more luxurious pre-flight experience.
-
B.
premium metro cabin class
A premium metro cabin class is an upgraded section of a metro train offering enhanced comfort, amenities, and exclusivity compared to standard cabins.
-
C.
airline cabin class
An airline cabin class is a categorization of seating and service levels on an aircraft (such as economy, premium economy, business, and first class) that defines the comfort, amenities, and pricing offered to passengers.
-
D.
premium economy cabin product
A premium economy cabin product is an airline seating class that offers enhanced comfort, space, and amenities compared to standard economy, at a lower price and service level than business class.
-
E.
premium cabin product
chosen
A premium cabin product is an enhanced airline seating and service offering that provides superior comfort, amenities, and personalized experiences compared to standard economy class.
- F. None of above.
Provenance (1 batch)
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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:06 p.m.