Triple
T15034131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBC One continuity suite |
E378436
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | broadcast control facility |
C34677
|
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: broadcast control facility Context triple: [BBC One continuity suite, instanceOf, broadcast control facility]
-
A.
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.
-
B.
broadcast regulator
A broadcast regulator is an authority or organization responsible for overseeing and enforcing rules, standards, and policies governing radio, television, and other broadcast media to ensure compliance with legal, ethical, and public interest requirements.
-
C.
broadcast station
A broadcast station is a facility equipped to transmit audio, video, or data content over radio, television, or digital channels to a dispersed audience.
-
D.
broadcast television station
A broadcast television station is a facility that produces, assembles, and transmits television programming over the airwaves to be received by the general public within a designated coverage area.
-
E.
broadcast infrastructure provider
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.
- F. None of above. chosen
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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:59 a.m.