Triple
T16401049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SkyTeam lounges |
E398309
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airline alliance lounge brand |
C1909
|
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 alliance lounge brand Context triple: [SkyTeam lounges, instanceOf, airline alliance lounge brand]
-
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.
airline brand
An airline brand is the distinct identity and perception of an airline in the minds of customers, shaped by its visual design, service experience, reputation, and marketing communications.
-
C.
global airline alliance
chosen
A global airline alliance is a cooperative network of independent airlines that coordinate schedules, share services, and integrate frequent-flyer and marketing programs to offer passengers seamless international travel across their combined route systems.
-
D.
charter airline brand
A charter airline brand is a distinct identity under which an airline offers non-scheduled, often customized flight services for specific groups, tour operators, or events, emphasizing flexibility, exclusivity, and tailored travel experiences.
-
E.
airline association
An airline association is an organized group of airlines that collaborates to set industry standards, coordinate policies, and advocate for the collective interests of its member carriers.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:09 a.m.