Triple
T22513382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scripps Broadcasting division |
E556578
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | radio broadcasting company division |
C10412
|
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: radio broadcasting company division Context triple: [Scripps Broadcasting division, instanceOf, radio broadcasting company division]
-
A.
radio broadcasting company
chosen
A radio broadcasting company is an organization that produces, transmits, and distributes audio content over radio frequencies or digital streams to reach and engage a listening audience.
-
B.
radio syndication company
A radio syndication company acquires, produces, and distributes audio programs to multiple radio stations or platforms, managing rights, advertising, and delivery to broaden a show's audience and revenue.
-
C.
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.
-
D.
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.
-
E.
radio network
A radio network is a communication system in which multiple radio transmitters and receivers are interconnected to exchange information wirelessly over shared frequency 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.