Triple
T22819070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITU-T G.983 series |
E565179
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | broadband access standard |
C2787
|
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: broadband access standard Context triple: [ITU-T G.983 series, instanceOf, broadband access standard]
-
A.
G.hn standard
The G.hn standard is a unified home networking specification that enables high-speed data transmission over existing wiring infrastructures such as power lines, phone lines, and coaxial cables within a building.
-
B.
telecommunications standard
chosen
A telecommunications standard is an agreed-upon set of technical specifications and protocols that ensure compatibility, interoperability, and reliable communication across different telecom networks and devices.
-
C.
broadband subsidy program
A broadband subsidy program is a policy initiative that provides financial assistance to reduce the cost of internet service for eligible individuals, households, or communities to improve digital access and affordability.
-
D.
family of digital subscriber line technologies
A family of digital subscriber line technologies is a group of related high-speed data transmission methods that use existing telephone lines to deliver broadband internet and other digital services.
-
E.
Ethernet fronthaul standard
An Ethernet fronthaul standard defines the protocols, interfaces, and performance requirements for transporting radio access network (RAN) traffic between distributed radio units and centralized baseband units over Ethernet-based networks.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:33 p.m.