Triple
T8580269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odeon Cinemas |
E203154
|
entity |
| Predicate | hasCustomerProgram |
P13356
|
FINISHED |
| Object | loyalty schemes |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: loyalty schemes | Statement: [Odeon Cinemas, hasCustomerProgram, loyalty schemes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomerProgram Context triple: [Odeon Cinemas, hasCustomerProgram, loyalty schemes]
-
A.
hasMembershipProgram
chosen
Indicates that an entity offers or participates in a structured membership program, typically providing special access, benefits, or services to enrolled members.
-
B.
hasAwardProgram
Indicates that an entity maintains or offers a formal award or recognition program.
-
C.
hasContributorProgram
Indicates that an entity operates or participates in a formal program through which contributors can submit work, content, or support.
-
D.
hasBeverageProgram
Indicates that an entity offers, manages, or participates in an organized beverage-related offering or initiative.
-
E.
loyaltyProgramType
Indicates the specific category or kind of loyalty program associated with an entity (such as points-based, tiered, or subscription-based).
- F. None of above.
Provenance (3 batches)
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_69ca8328ebe481909a8c038fa79959b4 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbeb1a026c819089183f542eeb7837 |
completed | March 31, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69cbd11b13108190b07f8f161425a585 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:22 p.m.