Triple
T17334318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XP (Flying Blue) |
E420895
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | loyalty program metric |
C24066
|
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 metric Context triple: [XP (Flying Blue), instanceOf, loyalty program metric]
-
A.
Loyalty program status level
A loyalty program status level represents a tiered membership state assigned to a customer based on their accumulated activity or value, determining the specific benefits, rewards, and privileges they receive.
-
B.
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.
-
C.
rewards program
A rewards program is a structured system that incentivizes customer loyalty by granting points, discounts, or other benefits in return for repeat purchases or engagement.
-
D.
frequent flyer status-earning metric
chosen
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.
-
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.
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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:43 a.m.