Triple
T34079236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Select Executive |
E873987
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | customer loyalty program status level |
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: customer loyalty program status level Context triple: [Select Executive, instanceOf, customer loyalty program status level]
-
A.
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.
-
B.
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.
-
C.
membership status
Membership status represents the current state or level of an individual's affiliation with an organization, group, or service, such as active, inactive, pending, or suspended.
-
D.
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.
-
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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:52 a.m.