Triple
T16841146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBC Digital Radio |
E409413
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital radio service portfolio |
C37912
|
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: digital radio service portfolio Context triple: [BBC Digital Radio, instanceOf, digital radio service portfolio]
-
A.
digital radio brand
A digital radio brand is a conceptual class representing a company or label that designs, produces, and markets digital radio devices or services distinguished by shared identity, features, and positioning in the audio technology market.
-
B.
radio broadcast service
A radio broadcast service is a system that transmits audio content over radio frequencies from a central source to multiple receivers within a defined coverage area.
-
C.
internet radio platform
An internet radio platform is a digital service that streams curated audio content—such as music, talk shows, and podcasts—over the internet in real time or on demand to users across various devices.
-
D.
digital satellite television service
A digital satellite television service is a broadcast system that delivers compressed digital TV and audio channels to subscribers via signals transmitted from satellites to small dish antennas at their premises.
-
E.
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.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
Created at: April 10, 2026, 5:24 a.m.