Triple
T23265164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JMB Premier |
E588126
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | loyalty program elite status |
C33483
|
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: loyalty program elite status Context triple: [JMB Premier, instanceOf, loyalty program elite status]
-
A.
airline elite status benefit
An airline elite status benefit is a preferential service or perk—such as priority boarding, complimentary upgrades, bonus miles, or fee waivers—granted to frequent flyers who reach a designated loyalty tier with an airline.
-
B.
Loyalty program status level
chosen
A loyalty program status level represents a tiered membership state assigned to a customer based on their accumulated activity or value, determining the specific benefits, rewards, and privileges they receive.
-
C.
airline loyalty tier
An airline loyalty tier is a classification level within a frequent-flyer program that grants travelers escalating benefits and privileges based on their accumulated travel activity or spending with the airline.
-
D.
airline loyalty program requirement
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.
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.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 4:29 p.m.