Triple
T14275835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ofcom Broadcasting Code |
E353913
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | media regulation instrument |
C33696
|
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: media regulation instrument Context triple: [Ofcom Broadcasting Code, instanceOf, media regulation instrument]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
media freedom watchdog
A media freedom watchdog is an organization or entity that monitors, evaluates, and advocates for the protection of press freedom, journalistic independence, and access to information.
-
E.
media network
A media network is an interconnected system of organizations, platforms, and channels that produce, distribute, and share content across various media formats to reach and engage audiences.
- 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.