Triple
T27190613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITV regional production network |
E683464
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | broadcast infrastructure |
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 infrastructure Context triple: [ITV regional production network, instanceOf, broadcast infrastructure]
-
A.
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.
-
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 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.
-
D.
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.
-
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_69eefad140408190b8586fdebcf9af46 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:32 a.m.