Triple
T6363143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakura Lounge |
E143158
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | business class lounge |
C16197
|
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: business class lounge Context triple: [Sakura Lounge, instanceOf, business class lounge]
-
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.
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.
-
C.
airport lounge
chosen
An airport lounge is a designated, often exclusive area within an airport that offers travelers a comfortable place to relax, work, and access amenities such as seating, refreshments, Wi‑Fi, and sometimes showers or business services while waiting for their flights.
-
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.
airline travel class
An airline travel class is a categorization of seating and service levels on a flight, such as economy, premium economy, business, and first class, that determines a passenger’s comfort, amenities, and fare.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:32 p.m.