Triple
T9029805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | xDSL technologies |
E216139
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | broadband access technology |
C2279
|
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 technology Context triple: [xDSL technologies, instanceOf, broadband access technology]
-
A.
data connectivity technology
Data connectivity technology encompasses the tools, protocols, and infrastructure that enable seamless, secure, and reliable exchange of data between systems, applications, and devices across diverse networks and environments.
-
B.
network technology
chosen
Network technology encompasses the hardware, software, and protocols that enable devices and systems to connect, communicate, and exchange data over local and wide-area networks, including the internet.
-
C.
internet infrastructure component
An internet infrastructure component is a foundational hardware or software element—such as routers, switches, servers, cables, or protocols—that enables the transmission, routing, and reliable delivery of data across interconnected networks.
-
D.
telecommunications infrastructure component
A telecommunications infrastructure component is a physical or virtual element—such as cables, antennas, switches, or routers—that enables the transmission, routing, and management of voice, data, and multimedia communications across networks.
-
E.
Internet service
An Internet service is a digital offering that provides users with specific online functionality or resources over a network, such as communication, data storage, or content access.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:08 p.m.