Triple
T21227956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TIA-568 |
E523131
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | telecommunications cabling 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: telecommunications cabling standard Context triple: [TIA-568, instanceOf, telecommunications cabling standard]
-
A.
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.
-
B.
twisted pair cable category
A twisted pair cable category is a classification of copper cabling defined by performance standards (such as bandwidth and data rate) based on the construction and electrical characteristics of its twisted wire pairs.
-
C.
Category 6 augmented cable
A Category 6 augmented cable (Cat 6a) is a twisted-pair Ethernet cable standard designed to support 10 Gigabit Ethernet over copper up to 100 meters with improved performance and reduced crosstalk compared to Cat 6.
-
D.
T11 standard
T11 standard is a conceptual classification defining a specific set of technical, performance, or safety requirements that systems or components must meet to ensure compatibility and consistent operation within a given domain.
-
E.
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.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:44 p.m.