Triple
T35125930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qantas Business Rewards |
E1014302
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | business loyalty 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: business loyalty program Context triple: [Qantas Business Rewards, instanceOf, business loyalty program]
-
A.
loyalty-security program
A loyalty-security program is a structured system that simultaneously rewards customer or member engagement while implementing measures to protect their data, accounts, and interactions from security threats.
-
B.
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.
-
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.
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 program operator
A loyalty program operator is an entity that designs, manages, and administers customer rewards schemes, tracking member activity and coordinating benefits, incentives, and partner relationships to drive engagement and retention.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.