Triple
T31346611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nectar |
E799462
|
entity |
| Predicate | typicalEarningRate |
P129461
|
FINISHED |
| Object | 1 point per £1 at many partners |
—
|
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: 1 point per £1 at many partners | Statement: [Nectar, typicalEarningRate, 1 point per £1 at many partners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEarningRate Context triple: [Nectar, typicalEarningRate, 1 point per £1 at many partners]
-
A.
typicalRate
chosen
Indicates the standard or commonly expected rate at which something occurs, is charged, or is applied in a given context.
-
B.
careerEarningsApprox
Indicates an approximate total amount of money an entity has earned over the course of its career.
-
C.
compensationRate
Indicates the rate or amount of payment provided in exchange for a specified unit of work, time, or service.
-
D.
typicalAwardAmount
Indicates the usual or most common amount of an award given in this relationship.
-
E.
payScale
Indicates the compensation level or salary range assigned to an entity, typically reflecting its relative pay or grade within a structured system.
- 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_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:17 p.m.