Triple
T6120750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimbabwe Media Commission |
E136476
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | media regulatory body |
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: media regulatory body Context triple: [Zimbabwe Media Commission, instanceOf, media regulatory body]
-
A.
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.
-
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.
media industry body
A media industry body is an organization that represents and coordinates the interests, standards, and regulatory engagement of companies and professionals within the media sector.
-
D.
telecommunications regulator
A telecommunications regulator is a governmental or independent authority responsible for overseeing, licensing, and enforcing rules in the communications sector to ensure fair competition, consumer protection, and efficient use of spectrum and infrastructure.
-
E.
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.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:14 p.m.