Triple
T26136615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GrabRewards |
E659398
|
entity |
| Predicate | higherTierBenefits |
P151665
|
FINISHED |
| Object | higher earn rates |
—
|
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: higher earn rates | Statement: [GrabRewards, higherTierBenefits, higher earn rates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherTierBenefits Context triple: [GrabRewards, higherTierBenefits, higher earn rates]
-
A.
higherTierProvides
chosen
Indicates that an entity at a higher tier supplies, offers, or makes available some resource, service, or benefit to entities at lower tiers.
-
B.
isTopTierBenefit
Indicates that a benefit belongs to the highest or most premium level within a defined benefit hierarchy or structure.
-
C.
benefitsLevel
Indicates the degree or extent to which one entity gains advantages, support, or positive outcomes from another entity or action.
-
D.
higherTierAlternative
Indicates that one option serves as a superior or more advanced alternative to another within a tiered structure.
-
E.
hasUpperTier
Indicates that one entity occupies a higher or superior level, rank, or layer in a hierarchical structure relative to another entity.
- 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_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 26, 2026, 8:18 p.m.