Triple
T25809915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tims Rewards |
E650077
|
entity |
| Predicate | redemptionCategory |
P159297
|
FINISHED |
| Object | food |
—
|
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: food | Statement: [Tims Rewards, redemptionCategory, food]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redemptionCategory Context triple: [Tims Rewards, redemptionCategory, food]
-
A.
redemptionType
Indicates the manner or method by which something (such as a benefit, reward, or obligation) can be redeemed or fulfilled.
-
B.
redemptionOptions
Indicates the ways or methods by which something (such as points, credits, or vouchers) can be redeemed or exchanged for value.
-
C.
redeemedBy
Indicates that something (such as a code, voucher, coupon, or offer) has been claimed, exchanged, or converted into its associated benefit or value by a particular entity.
-
D.
seeksRedemption
Indicates that an entity is actively striving to atone for past wrongs or failures and restore its moral standing.
-
E.
redemptionScope
Indicates the range or conditions under which something (such as a benefit, offer, or obligation) can be redeemed or fulfilled.
- F. None of above. chosen
Provenance (4 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600c37d40819086cc056057c25629 |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 7:08 a.m.