Triple
T1684579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medallion Complimentary Upgrades (subject to rules) |
E36413
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airline loyalty benefit |
C8366
|
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 loyalty benefit Context triple: [Medallion Complimentary Upgrades (subject to rules), instanceOf, airline loyalty benefit]
-
A.
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.
-
B.
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.
-
C.
airline award
An airline award is a ticket or upgrade obtained using accumulated frequent-flyer miles or points instead of paying the full cash fare.
-
D.
airline loyalty tier
chosen
An airline loyalty tier is a classification level within a frequent-flyer program that grants travelers escalating benefits and privileges based on their accumulated travel activity or spending with the airline.
-
E.
driver rewards program
A driver rewards program is a system that incentivizes and recognizes drivers’ performance, safety, and loyalty through points, benefits, and exclusive offers.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:29 p.m.