Triple
T9029758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.fast |
E216138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital subscriber line technology |
C9032
|
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: digital subscriber line technology Context triple: [G.fast, instanceOf, digital subscriber line technology]
-
A.
digital line code
A digital line code is a method of representing digital data as a specific pattern of voltage, current, or light level changes over a transmission medium to enable reliable communication between devices.
-
B.
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.
-
C.
telecommunications network
A telecommunications network is a system of interconnected nodes, transmission media, and protocols that enables the exchange of voice, data, and multimedia information between users and devices over distance.
-
D.
digital satellite television service
A digital satellite television service is a broadcast system that delivers compressed digital TV and audio channels to subscribers via signals transmitted from satellites to small dish antennas at their premises.
-
E.
data connectivity technology
chosen
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.
- 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.