Triple
T4688870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian Lounge |
E103985
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airline lounge |
C1206
|
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: airline lounge Context triple: [Norwegian Lounge, instanceOf, airline lounge]
-
A.
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.
-
B.
premium airport lounge
chosen
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.
-
C.
passenger terminal concourse
A passenger terminal concourse is a large, central circulation space within a transport terminal where travelers move between entrances, ticketing, security, and boarding areas, often containing seating, retail, and information services.
-
D.
airport services provider
An airport services provider is an organization that delivers ground handling, passenger assistance, cargo management, and related operational support services to airlines and airport authorities.
-
E.
airport service area
An airport service area is the designated zone within and around an airport where operational, maintenance, and support activities are conducted to facilitate aircraft handling and passenger services.
- 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:16 p.m.