Triple
T9855512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Membership Rewards |
E239574
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | credit card rewards program |
C10240
|
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: credit card rewards program Context triple: [Membership Rewards, instanceOf, credit card rewards program]
-
A.
rewards program
chosen
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.
-
B.
travel rewards credit card
A travel rewards credit card is a payment card that earns points, miles, or cash back on purchases—often with bonus rewards on travel-related spending—and provides travel-focused benefits such as airline or hotel perks, trip protections, and no foreign transaction fees.
-
C.
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.
-
D.
co-branded airline rewards credit card
A co-branded airline rewards credit card is a payment card issued jointly by a bank and an airline that lets cardholders earn airline-specific miles or points and enjoy related travel perks on their everyday spending.
-
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_69ca84e6493081909cf58c8d42ea856b |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:35 p.m.