Triple
T4893358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. International Broadcasting Act |
E109615
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | broadcasting law |
C16003
|
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 law Context triple: [U.S. International Broadcasting Act, instanceOf, broadcasting law]
-
A.
broadcasting regulator
A broadcasting regulator is an authority or agency responsible for overseeing and enforcing rules, standards, and policies governing radio, television, and other broadcast media to ensure compliance with legal, ethical, and public interest requirements.
-
B.
communications law
chosen
Communications law is the body of legal rules and regulations governing the transmission of information and content via electronic media, including broadcasting, telecommunications, and digital networks.
-
C.
broadcast licensee
A broadcast licensee is an individual or organization that holds legal authorization from a regulatory authority to operate a radio, television, or other broadcast service on specified frequencies or channels.
-
D.
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.
-
E.
broadcast regulator
A broadcast regulator is an authority or organization responsible for overseeing and enforcing rules, standards, and policies governing radio, television, and other broadcast media to ensure compliance with legal, ethical, and public interest requirements.
- 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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:28 p.m.