Triple
T32187740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daily Cash |
E822151
|
entity |
| Predicate | rewardRateMaximum |
P9530
|
FINISHED |
| Object | 3 percent of purchase amount |
—
|
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 of purchase amount | Statement: [Daily Cash, rewardRateMaximum, 3 percent of purchase amount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardRateMaximum Context triple: [Daily Cash, rewardRateMaximum, 3 percent of purchase amount]
-
A.
rateConstraint
Indicates a limitation or bound on the rate at which a process, transaction, or interaction is allowed to occur.
-
B.
maxCurrent
Indicates the maximum electric current that is allowed to flow through or be drawn by an entity under specified conditions.
-
C.
maximumUsage
Indicates the highest allowable or observed amount, frequency, or extent to which something can be used within a defined context or period.
-
D.
increasedRateOn
Indicates that one entity has raised the rate, fee, or charge applied to another entity.
-
E.
setsMaximum
chosen
Indicates that one entity establishes an upper limit or maximum allowable value for another entity or quantity.
- 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_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_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:35 a.m.