Triple
T22818798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Plus |
E565170
|
entity |
| Predicate | pointCurrency |
P245
|
FINISHED |
| Object | Canadian Plus 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: Canadian Plus points | Statement: [Canadian Plus, pointCurrency, Canadian Plus points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointCurrency Context triple: [Canadian Plus, pointCurrency, Canadian Plus points]
-
A.
positionOnCurrency
Indicates the role or placement an entity holds on a specific unit of currency (e.g., whose image or symbol appears on a bill or coin).
-
B.
formerPointsCurrency
Indicates that a points-based currency previously used in a loyalty or rewards program has been discontinued or replaced.
-
C.
pegTargetCurrency
Indicates that one currency’s value is fixed or tightly linked to the value of a specified target currency.
-
D.
currencyPeg
Indicates that one currency’s value is fixed or tightly linked to the value of another currency or a basket of currencies.
-
E.
currency
chosen
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dce762c8190934fb921f942c9fd |
completed | April 29, 2026, 3:41 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:33 p.m.