Triple
T15836191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITU Region 2 |
E383988
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | radio regulation region |
C35884
|
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: radio regulation region Context triple: [ITU Region 2, instanceOf, radio regulation region]
-
A.
radio frequency band
A radio frequency band is a specific range of electromagnetic spectrum frequencies allocated for particular types of wireless communication or broadcasting services.
-
B.
radio quiet zone
A radio quiet zone is a designated geographic area where radio transmissions are heavily restricted or minimized to protect sensitive radio astronomy or communication facilities from interference.
-
C.
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.
-
D.
broadcasting regulation
Broadcasting regulation is the set of laws, policies, and oversight mechanisms that govern how radio, television, and related media services operate, including licensing, content standards, ownership rules, and public interest obligations.
-
E.
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.
- F. None of above. chosen
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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:49 a.m.