Triple
T28400294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Synchronous Digital Hierarchy |
E719378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fiber-optic transport technology |
C29616
|
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: fiber-optic transport technology Context triple: [Synchronous Digital Hierarchy, instanceOf, fiber-optic transport technology]
-
A.
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.
-
B.
optical transceiver form factor
An optical transceiver form factor is a standardized physical and electrical interface specification that defines the size, shape, connector type, and pin configuration of pluggable optical modules used in networking and communication equipment.
-
C.
optical technology
chosen
Optical technology encompasses devices and systems that generate, manipulate, transmit, or detect light to enable applications such as imaging, communication, sensing, and information processing.
-
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.
FDDI variant
An FDDI variant is a modified implementation of the Fiber Distributed Data Interface standard that adapts its dual-ring, high-speed token-passing architecture to alternative media, topologies, or performance requirements.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:19 a.m.