Triple
T31346577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nectar |
E799462
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coalition loyalty scheme |
C458
|
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: coalition loyalty scheme Context triple: [Nectar, instanceOf, coalition loyalty scheme]
-
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.
coalition
chosen
A coalition is a temporary or long-term alliance of individuals, groups, or organizations that coordinate their resources and actions to achieve shared goals or exert collective influence.
-
C.
loyalty review board
A loyalty review board is an authoritative body that evaluates individuals’ or organizations’ allegiance, reliability, and adherence to established values or policies, often to determine trust, privileges, or continued membership.
-
D.
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.
-
E.
rewards program
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.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:17 p.m.