Triple
T30396195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Television and Radio Broadcasting Network |
E773224
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | broadcasting network operator |
C12990
|
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: broadcasting network operator Context triple: [Russian Television and Radio Broadcasting Network, instanceOf, broadcasting network operator]
-
A.
television network operator
A television network operator is an organization that manages, schedules, and distributes television programming across broadcast, cable, satellite, or digital platforms to reach viewers.
-
B.
broadcast infrastructure provider
chosen
A broadcast infrastructure provider is an organization that designs, builds, operates, and maintains the technical networks and facilities required to transmit audio, video, and data content from broadcasters to end audiences across various distribution platforms.
-
C.
television network
A television network is an organization that produces, acquires, schedules, and distributes television programming across multiple stations or platforms under a unified brand.
-
D.
broadcaster
A broadcaster is an entity that transmits audio, video, or data content from a single source to a wide audience through various communication channels such as radio, television, or digital streaming platforms.
-
E.
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.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:02 p.m.