Triple
T33319767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlusPoints upgrade currency |
E853106
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | frequent‑flyer program benefit |
C61536
|
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: frequent‑flyer program benefit Context triple: [PlusPoints upgrade currency, instanceOf, frequent‑flyer program benefit]
-
A.
frequent-flyer program
A frequent-flyer program is a customer loyalty scheme offered by an airline that rewards passengers with points or miles for their flights and related purchases, which can be redeemed for benefits such as free flights, upgrades, and priority services.
-
B.
airline elite status benefit
An airline elite status benefit is a preferential service or perk—such as priority boarding, complimentary upgrades, bonus miles, or fee waivers—granted to frequent flyers who reach a designated loyalty tier with an airline.
-
C.
airline loyalty program
An airline loyalty program is a customer rewards system that allows passengers to earn and redeem points or miles for flights and related travel benefits based on their travel activity and tier status.
-
D.
travel loyalty program
A travel loyalty program is a structured system offered by travel providers that rewards customers with points, miles, or status benefits for their continued use of the provider’s services.
-
E.
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.
- F. None of above. chosen
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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:33 a.m.