Triple
T17005586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hero Miles program |
E412561
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | frequent flyer mile donation program |
C1374
|
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: frequent flyer mile donation program Context triple: [Hero Miles program, instanceOf, frequent flyer mile donation program]
-
A.
frequent-flyer program
chosen
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.
-
B.
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.
-
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.
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.
-
E.
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.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:32 a.m.