Triple
T13780687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurovision Services |
E331123
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | broadcast services provider |
C3468
|
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 services provider Context triple: [Eurovision Services, instanceOf, broadcast services provider]
-
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.
public service broadcasting
Public service broadcasting is a media system, typically funded by the public or through license fees, that provides impartial, high-quality content designed to inform, educate, and entertain while serving the democratic, cultural, and social needs of society rather than commercial interests.
-
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.
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.
-
E.
broadcaster
chosen
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.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:11 p.m.