Triple
T10413647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Canada Aeroplan Super Elite |
E245458
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airline elite status |
C7018
|
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 elite status Context triple: [Air Canada Aeroplan Super Elite, instanceOf, airline elite status]
-
A.
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.
-
B.
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.
-
C.
frequent flyer status-earning metric
A frequent flyer status-earning metric is a quantified measure (such as miles, segments, or points) that tracks a traveler’s progress toward achieving or maintaining elite status in an airline loyalty program.
-
D.
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.
-
E.
airline loyalty program requirement
An airline loyalty program requirement is a specific condition or set of criteria that a customer must meet—such as miles flown, segments traveled, or spending thresholds—to earn, maintain, or use loyalty benefits and status tiers.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:10 p.m.