Triple
T37480300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITU-R Study Group 6 |
E931394
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ITU-R study group |
C10617
|
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: ITU-R study group Context triple: [ITU-R Study Group 6, instanceOf, ITU-R study group]
-
A.
ITU-R recommendation
An ITU-R recommendation is an internationally agreed technical standard or guideline issued by the ITU Radiocommunication Sector to ensure the efficient, compatible, and harmonized use of the radio-frequency spectrum and satellite orbits.
-
B.
ITU-T Recommendation
An ITU-T Recommendation is an internationally agreed technical standard developed by the ITU Telecommunication Standardization Sector to ensure the interoperability, quality, and efficiency of global telecommunication networks and services.
-
C.
subsidiary body of ITU‑D
A subsidiary body of ITU‑D is an organizational entity established under the ITU Telecommunication Development Sector to carry out specialized tasks, studies, or advisory functions that support and implement ITU‑D’s development objectives and programs.
-
D.
telecommunications committee
chosen
A telecommunications committee is a group responsible for overseeing, planning, and guiding policies, standards, and initiatives related to communication networks and technologies within an organization or governing body.
-
E.
IRTF research group
An IRTF research group is a collaborative team within the Internet Research Task Force that investigates long-term, exploratory topics related to the evolution and future of Internet technologies.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.