Triple
T30786802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Professional Media over IP Networks |
E783976
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | broadcast engineering concept |
C35887
|
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: broadcast engineering concept Context triple: [Professional Media over IP Networks, instanceOf, broadcast engineering concept]
-
A.
broadcast engineering tool
A broadcast engineering tool is a specialized software or hardware solution used to design, monitor, test, and maintain audio/video signal chains and transmission systems for professional broadcast environments.
-
B.
broadcast technology
chosen
Broadcast technology encompasses the systems, equipment, and protocols used to transmit audio, video, and data content from a central source to dispersed audiences over various media channels such as radio, television, and digital networks.
-
C.
broadcast control facility
A broadcast control facility is a centralized location equipped with the systems and personnel needed to manage, monitor, and direct the transmission and routing of broadcast audio and video content.
-
D.
broadcast infrastructure provider
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.
-
E.
broadcast station
A broadcast station is a facility equipped to transmit audio, video, or data content over radio, television, or digital channels to a dispersed audience.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:41 p.m.