Triple
T12673653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boots |
E302747
|
entity |
| Predicate | Boots Advantage Card |
P11672
|
FINISHED |
| Object | loyalty program |
—
|
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 program | Statement: [Boots, Boots Advantage Card, loyalty program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Boots Advantage Card Context triple: [Boots, Boots Advantage Card, loyalty program]
-
A.
cardEligibility
Indicates whether an entity qualifies for or is allowed to receive a particular card under specified criteria.
-
B.
loyaltySymbolizedBy
Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
-
C.
supportsLoyaltyCards
chosen
Indicates that an entity provides functionality to accept, manage, or work with loyalty cards for rewards or benefits.
-
D.
loyaltyProgramPartner
Indicates that there is a partnership or affiliation between entities within the same loyalty or rewards program.
-
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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961af991c8190b6079cb57e593b8f |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:20 p.m.