Triple
T28249594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MQMs |
E712277
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Delta Air Lines loyalty program component |
C24065
|
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: Delta Air Lines loyalty program component Context triple: [MQMs, instanceOf, Delta Air Lines loyalty program component]
-
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.
IATA program
An IATA program is an organized set of standards, training, and regulatory frameworks developed by the International Air Transport Association to enhance safety, efficiency, and consistency across global air transport operations.
-
D.
airline loyalty program requirement
chosen
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.
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.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:03 p.m.