Triple
T18861606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBS Television Stations |
E461324
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | broadcasting company division |
C36973
|
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 company division Context triple: [CBS Television Stations, instanceOf, broadcasting company division]
-
A.
television broadcasting company division
A television broadcasting company division is an organizational unit within a broadcasting company responsible for managing specific channels, content genres, regional operations, or functional areas such as programming, production, or distribution.
-
B.
television broadcasting division
The television broadcasting division is the organizational unit responsible for planning, producing, scheduling, and transmitting television content to audiences across designated channels and platforms.
-
C.
division of CBS
chosen
A division of CBS is a major organizational unit within the Columbia Broadcasting System responsible for managing a specific set of media operations, content areas, or business functions under the broader CBS corporate structure.
-
D.
broadcasting union
A broadcasting union is an organization that represents and advocates for the collective rights, working conditions, and professional interests of workers in the broadcasting and media industry.
-
E.
broadcasting headquarters
A broadcasting headquarters is a central facility where television, radio, and digital media content is produced, managed, and transmitted to audiences across various distribution channels.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:57 a.m.