Triple
T13780730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARD |
E331124
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public broadcasting consortium |
C20234
|
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: public broadcasting consortium Context triple: [ARD, instanceOf, public broadcasting consortium]
-
A.
broadcasting union
A broadcasting union is an organization that represents and advocates for the collective rights, working conditions, and professional interests of workers in the broadcasting and media industry.
-
B.
public consortium
chosen
A public consortium is a collaborative alliance of multiple public or publicly accountable organizations that pool resources, expertise, and governance to pursue shared goals or projects in the public interest.
-
C.
private consortium
A private consortium is a collaborative alliance of independent, typically private-sector organizations that pool resources, expertise, and decision-making authority to pursue shared objectives while remaining legally distinct entities.
-
D.
public broadcaster
A public broadcaster is a media organization funded and regulated by the public (typically through taxes, license fees, or government support) to provide impartial, diverse, and universally accessible content in the public interest rather than for commercial profit.
-
E.
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.
- 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.