Triple
T32187764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daily Cash |
E822151
|
entity |
| Predicate | rewardPostingMethod |
P174140
|
FINISHED |
| Object | automatic |
—
|
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: automatic | Statement: [Daily Cash, rewardPostingMethod, automatic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardPostingMethod Context triple: [Daily Cash, rewardPostingMethod, automatic]
-
A.
rewardModel
Indicates a relationship where one entity serves as a model or framework for assigning rewards or evaluating outcomes for another entity or process.
-
B.
rewardMechanism
Indicates a relationship where an entity provides or defines a system of incentives or compensation in response to certain actions, behaviors, or outcomes.
-
C.
rewardRecipient
Indicates the entity that receives a reward as a result of some action, event, or decision.
-
D.
rewardUnit
Indicates that one entity serves as the unit or measure in which a reward is quantified or granted to another entity.
-
E.
rewardSignal
Indicates that one entity provides a signal representing feedback or incentive (such as a reward or penalty) to guide another entity’s behavior or learning process.
- 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_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:35 a.m.