Triple
T8079850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Movie and Television Review and Classification Board |
E188586
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | television content regulator |
C12316
|
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 content regulator Context triple: [Movie and Television Review and Classification Board, instanceOf, television content regulator]
-
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.
media regulator
chosen
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.
-
C.
television institute
A television institute is an educational and research organization dedicated to the study, training, and development of skills and technologies related to television production, broadcasting, and media arts.
-
D.
television channel
A television channel is a dedicated broadcast or streaming outlet that delivers a curated sequence of video and audio programs to an audience under a specific brand or theme.
-
E.
television review aggregator
A television review aggregator is a platform that collects, organizes, and summarizes critics’ and viewers’ ratings and reviews of TV shows to provide an overall assessment and comparative insights.
- 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:28 p.m.