Triple
T24791223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SJR |
E620254
|
entity |
| Predicate | underlyingCompanyOperatesBrand |
P6745
|
FINISHED |
| Object | Shaw Cable |
—
|
NE NERFINISHED |
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: Shaw Cable | Statement: [SJR, underlyingCompanyOperatesBrand, Shaw Cable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingCompanyOperatesBrand Context triple: [SJR, underlyingCompanyOperatesBrand, Shaw Cable]
-
A.
hasUnderlyingCompanyBrand
Indicates that one entity is associated with or operates under the corporate brand of another company as its underlying brand.
-
B.
operatedByBrand
Indicates that an entity (such as a service, location, or product line) is run, managed, or controlled by a particular brand.
-
C.
operatedByCompany
Indicates that an entity is run, managed, or controlled by a specific company.
-
D.
underlyingCompany
chosen
Indicates that one entity serves as the fundamental or base company upon which another entity (such as a product, instrument, or structure) is built, derived, or dependent.
-
E.
parentBrand
Indicates that one brand is the overarching or owning brand from which another brand is derived or subordinated.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 4:47 a.m.