Triple
T27916909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telesat Canada |
E706099
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | broadcasting services provider |
C12990
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: broadcasting services provider Context triple: [Telesat Canada, instanceOf, broadcasting services provider]
-
A.
broadcast infrastructure provider
chosen
A broadcast infrastructure provider is an organization that designs, builds, operates, and maintains the technical networks and facilities required to transmit audio, video, and data content from broadcasters to end audiences across various distribution platforms.
-
B.
media services provider
A media services provider is an organization that creates, manages, distributes, or facilitates access to audio, video, and digital content across various platforms and channels.
-
C.
public service broadcasting
Public service broadcasting is a media system, typically funded by the public or through license fees, that provides impartial, high-quality content designed to inform, educate, and entertain while serving the democratic, cultural, and social needs of society rather than commercial interests.
-
D.
pay television broadcaster
A pay television broadcaster is a media company that transmits television content to subscribers who pay for access, often offering premium or specialized channels not available on free-to-air TV.
-
E.
cable television provider
A cable television provider is a company that delivers television programming and related services to customers via coaxial or fiber-optic cable networks, often bundling internet and phone services.
- F. None of above.
Provenance (1 batch)
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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 6:54 p.m.