Triple
T32187741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daily Cash |
E822151
|
entity |
| Predicate | rewardRate |
P173832
|
FINISHED |
| Object | 3 percent on purchases directly with Apple |
—
|
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: 3 percent on purchases directly with Apple | Statement: [Daily Cash, rewardRate, 3 percent on purchases directly with Apple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardRate Context triple: [Daily Cash, rewardRate, 3 percent on purchases directly with Apple]
-
A.
rewardTiming
Indicates the point in time or schedule at which a reward is given relative to the triggering action or condition.
-
B.
rate
Indicates the numerical evaluation or assessment assigned by one entity to another based on perceived quality, performance, or value.
-
C.
rewardUnit
Indicates that one entity serves as the unit or measure in which a reward is quantified or granted to another entity.
-
D.
exportRate
Indicates the rate or proportion at which goods, services, or resources are sent out from one entity or region to others.
-
E.
successRate
Indicates the proportion or frequency with which attempts at a given action or process result in a successful outcome.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6babc938c8190a233c3a8b5254802 |
completed | May 3, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:35 a.m.