Triple
T31346586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nectar |
E799462
|
entity |
| Predicate | currencyOfPoints |
P66085
|
FINISHED |
| Object | Nectar points |
—
|
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: Nectar points | Statement: [Nectar, currencyOfPoints, Nectar points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyOfPoints Context triple: [Nectar, currencyOfPoints, Nectar points]
-
A.
loyaltyCurrencyUse
Indicates the use or redemption of loyalty program currency (such as points or miles) in a transaction or activity.
-
B.
loyaltyCurrencyProgram
chosen
Indicates a relationship where an entity participates in or is associated with a loyalty or rewards currency program that tracks and grants benefits based on activity or purchases.
-
C.
earnsRewardsCurrency
Indicates that an entity receives or accumulates a specified rewards currency as a result of some action, status, or relationship.
-
D.
currencyUsedFor
Indicates that a particular currency is used as the medium of exchange or legal tender for a given entity, such as a country, region, or organization.
-
E.
currencyGiven
Indicates that one entity transfers or provides money or a monetary unit 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: April 29, 2026, 9:17 p.m.