Triple
T15146789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kicking Horse Coffee |
E361828
|
entity |
| Predicate | sourcing |
P53073
|
FINISHED |
| Object | Arabica beans |
—
|
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: Arabica beans | Statement: [Kicking Horse Coffee, sourcing, Arabica beans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourcing Context triple: [Kicking Horse Coffee, sourcing, Arabica beans]
-
A.
productSourcingStrategy
Indicates the approach or method by which a product is obtained or sourced, such as from suppliers, manufacturers, or other channels.
-
B.
materialSource
chosen
Indicates that one entity serves as the origin or provider of the material or substance used by another entity.
-
C.
supplyChain
Indicates a relationship where one entity participates in providing, transferring, or managing goods, services, or information to another as part of a sequential production and distribution process.
-
D.
source
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
E.
supplyRole
Indicates that an entity provides or fulfills a specific role within a supply or provisioning relationship 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005c825a481909d00098b0e743365 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:07 a.m.