Triple
T14131332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burgundy |
E350173
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Loyalty program status level |
C33483
|
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: Loyalty program status level Context triple: [Burgundy, instanceOf, Loyalty program status level]
-
A.
airline loyalty tier
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.
-
B.
loyalty points currency
A loyalty points currency is a digital or symbolic unit of value issued by a brand or program that customers earn through engagement or purchases and can redeem for rewards, discounts, or services.
-
C.
airline loyalty program qualification metric
A airline loyalty program qualification metric is a measurable criterion—such as miles flown, segments flown, or dollars spent—used to determine a traveler’s eligibility for earning, maintaining, or advancing status within an airline’s loyalty program.
-
D.
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.
-
E.
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.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 9, 2026, 11:03 p.m.