Triple
T14275884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ofcom Broadcasting Code on the Scheduling of Television Advertising |
E353914
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | television advertising regulation |
C33698
|
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: television advertising regulation Context triple: [Ofcom Broadcasting Code on the Scheduling of Television Advertising, instanceOf, television advertising regulation]
-
A.
broadcasting regulator
A broadcasting regulator is an authority or agency 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.
-
B.
television commercial
A television commercial is a short, paid video advertisement broadcast on TV to promote products, services, or ideas to a targeted audience.
-
C.
media regulator
A media regulator is an authority or organization responsible for overseeing and enforcing rules, standards, and policies governing media content, ownership, and distribution to protect the public interest.
-
D.
television industry
The television industry encompasses the businesses, technologies, and creative processes involved in producing, distributing, and monetizing television content across broadcast, cable, and streaming platforms.
-
E.
television market
A television market is a defined geographic area in which television stations and providers compete to deliver broadcast and cable programming to viewers and sell advertising based on that audience.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:10 a.m.