Triple
T31385699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galleries |
E800587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airport lounge product |
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: airport lounge product Context triple: [Galleries, instanceOf, airport lounge product]
-
A.
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.
-
B.
airport lounge brand
An airport lounge brand is a distinct identity and service concept that offers travelers a consistent, premium pre-flight experience across one or more lounges, defined by its amenities, ambiance, and membership or access model.
-
C.
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.
-
D.
private aviation terminal
A private aviation terminal is a specialized airport facility that provides exclusive, streamlined services and amenities for private and corporate aircraft, their passengers, and crews.
-
E.
premium cabin product
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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
Created at: April 29, 2026, 9:19 p.m.