Triple
T29641940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet radio |
E755884
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state-controlled broadcasting system |
C7538
|
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: state-controlled broadcasting system Context triple: [Soviet radio, instanceOf, state-controlled broadcasting system]
-
A.
state-owned broadcaster
chosen
A state-owned broadcaster is a media organization that is owned, funded, or controlled by a government to produce and distribute radio, television, or digital content to the public.
-
B.
broadcast television system
A broadcast television system is an integrated network of equipment, standards, and transmission channels that captures, encodes, and distributes audiovisual content over the air or via cable/satellite to multiple receivers simultaneously.
-
C.
broadcast television station
A broadcast television station is a facility that produces, assembles, and transmits television programming over the airwaves to be received by the general public within a designated coverage area.
-
D.
broadcasting council
A broadcasting council is a governing or advisory body responsible for overseeing, regulating, and guiding the policies, standards, and strategic direction of broadcasting services within a specific jurisdiction or organization.
-
E.
state-controlled network of organizations
A state-controlled network of organizations is a coordinated system of entities whose structures, activities, and decision-making are centrally directed or heavily influenced by government authorities to achieve political, economic, or social objectives.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
Created at: April 28, 2026, 6:47 p.m.