Triple
T17364504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Family of the United Kingdom (VIP transport) |
E422152
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | VIP air transport service |
C14050
|
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: VIP air transport service Context triple: [Royal Family of the United Kingdom (VIP transport), instanceOf, VIP air transport service]
-
A.
VIP terminal
A VIP terminal is an exclusive airport facility that offers private, expedited, and luxurious services for high-profile travelers, including dedicated check-in, security, lounges, and transport to aircraft.
-
B.
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.
-
C.
premium travel benefit
A premium travel benefit is an exclusive perk or service—such as lounge access, priority boarding, upgrades, or travel credits—provided to enhance comfort, convenience, and value for eligible travelers.
-
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.
air transport service provider
chosen
An air transport service provider is an organization that offers the commercial operation, management, and coordination of aircraft and related services to move passengers or cargo between locations.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:44 a.m.