Triple
T22360364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Tire Bank |
E552762
|
entity |
| Predicate | offersDigitalChannel |
P71475
|
FINISHED |
| Object | online account access |
—
|
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: online account access | Statement: [Canadian Tire Bank, offersDigitalChannel, online account access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersDigitalChannel Context triple: [Canadian Tire Bank, offersDigitalChannel, online account access]
-
A.
digitalChannelType
Indicates the type or category of digital channel through which an interaction, communication, or transaction occurs.
-
B.
availabilityChannel
chosen
Indicates the medium or channel through which something (such as a product, service, or resource) is made available or can be accessed.
-
C.
digitalProvider
Indicates that one entity serves as the supplier or source of digital services, content, or infrastructure for another entity.
-
D.
offersInterface
Indicates that one entity provides or exposes a specific interface that another entity can use or interact with.
-
E.
offersProcedure
Indicates that one entity provides or makes available a specific procedure 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157d3852c819082518851568e1b51 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.