Triple
T7104557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Co-op Food |
E165543
|
entity |
| Predicate | hasLoyaltyScheme |
P13356
|
FINISHED |
| Object | Co-op Membership |
—
|
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: Co-op Membership | Statement: [Co-op Food, hasLoyaltyScheme, Co-op Membership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLoyaltyScheme Context triple: [Co-op Food, hasLoyaltyScheme, Co-op Membership]
-
A.
loyaltyProgramType
Indicates the specific category or kind of loyalty program associated with an entity (such as points-based, tiered, or subscription-based).
-
B.
hasMembershipProgram
chosen
Indicates that an entity offers or participates in a structured membership program, typically providing special access, benefits, or services to enrolled members.
-
C.
loyaltySymbolizedBy
Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
-
D.
loyaltyMechanism
Indicates a mechanism or process through which loyalty is established, maintained, or reinforced between entities.
-
E.
loyaltyIncentive
Indicates a relationship where benefits or rewards are provided to encourage or recognize continued commitment or repeat engagement.
- 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_69c6887fcddc8190a5d58908f6dee590 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e58b3f708190bebca7d4c4db40f2 |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:42 p.m.