Triple
T26136601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GrabRewards |
E659398
|
entity |
| Predicate | pointsEarnedBy |
P62973
|
FINISHED |
| Object | using GrabPay Card where available |
—
|
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: using GrabPay Card where available | Statement: [GrabRewards, pointsEarnedBy, using GrabPay Card where available]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsEarnedBy Context triple: [GrabRewards, pointsEarnedBy, using GrabPay Card where available]
-
A.
pointsEarnedFrom
chosen
Indicates the number of points that an entity has received as a result of another specified source, action, or event.
-
B.
winnerPoints
Indicates the number of points earned by the winning participant or entity in a competition or event.
-
C.
pointsForWin
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
D.
careerPoints
Indicates the total number of points an individual has accumulated over the course of their entire career in a given activity or domain.
-
E.
pointsScored
Indicates the number of points an entity has earned or achieved in a particular event, game, or context.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60b97942c8190b3d913dcdcd30e08 |
completed | May 2, 2026, 2:35 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:18 p.m.