Triple
T37882491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogers Broadcasting |
E944903
|
entity |
| Predicate | operatedTelevisionBrand |
P197407
|
FINISHED |
| Object | Citytv |
E59609
|
NE 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: Citytv | Statement: [Rogers Broadcasting, operatedTelevisionBrand, Citytv]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedTelevisionBrand Context triple: [Rogers Broadcasting, operatedTelevisionBrand, Citytv]
-
A.
televisionShowBrand
Indicates that a brand is associated with, sponsors, or is featured within a particular television show.
-
B.
hasTelevisionChannelBrand
Indicates that an entity is associated with or operates under a particular television channel brand.
-
C.
operatedByBrand
Indicates that an entity (such as a service, location, or product line) is run, managed, or controlled by a particular brand.
-
D.
operatedChannelBrand
chosen
Indicates that a brand is responsible for operating or managing a particular channel.
-
E.
televisionPlatform
Indicates that one entity serves as the television platform (e.g., service, system, or distribution channel) through which the other entity’s TV content is delivered or accessed.
- F. None of above.
Provenance (4 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a03173dd4988190a38175b63cba9f09 |
completed | May 12, 2026, 12:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41042ee8788190a3c89dcc9a8b6f45 |
completed | June 28, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_6a031700ade88190afd217d5966b03b4 |
completed | May 12, 2026, 12:03 p.m. |
Created at: May 3, 2026, 4:19 p.m.