Triple
T8269982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell Media |
E193402
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | telecommunications subsidiary |
C16705
|
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: telecommunications subsidiary Context triple: [Bell Media, instanceOf, telecommunications subsidiary]
-
A.
telecommunications company
A telecommunications company is an organization that provides communication services such as voice, data, and video transmission over wired or wireless networks to individuals and businesses.
-
B.
telecommunications organization
chosen
A telecommunications organization is an entity that provides communication services and infrastructure—such as voice, data, and internet connectivity—across distances using wired, wireless, or satellite networks.
-
C.
telecommunications network
A telecommunications network is a system of interconnected nodes, transmission media, and protocols that enables the exchange of voice, data, and multimedia information between users and devices over distance.
-
D.
telecommunications infrastructure component
A telecommunications infrastructure component is a physical or virtual element—such as cables, antennas, switches, or routers—that enables the transmission, routing, and management of voice, data, and multimedia communications across networks.
-
E.
telecommunications regulator
A telecommunications regulator is a governmental or independent authority responsible for overseeing, licensing, and enforcing rules in the communications sector to ensure fair competition, consumer protection, and efficient use of spectrum and infrastructure.
- 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:50 p.m.