Triple
T17381887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flying Club miles |
E422588
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | frequent-flyer currency |
C13812
|
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 currency Context triple: [Flying Club miles, instanceOf, frequent-flyer currency]
-
A.
travel rewards currency
chosen
A travel rewards currency is a points or miles system issued by airlines, hotels, or credit cards that can be accumulated and redeemed for travel-related benefits such as flights, accommodations, and upgrades.
-
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.
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.
-
D.
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.
-
E.
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.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:45 a.m.