Triple
T28400293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Synchronous Digital Hierarchy |
E719378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital transmission hierarchy |
C54010
|
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 transmission hierarchy Context triple: [Synchronous Digital Hierarchy, instanceOf, digital transmission hierarchy]
-
A.
digital broadcasting standard family
A digital broadcasting standard family is a group of related technical specifications that define how audio, video, and data are encoded, transmitted, and received over digital broadcast media to ensure interoperability and consistent quality across devices and services.
-
B.
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.
-
C.
digital multicast television network
A digital multicast television network is a broadcast system that transmits multiple distinct digital TV channels or streams simultaneously over a single frequency or network connection.
-
D.
IP video transport standard
An IP video transport standard defines the protocols, formats, and procedures for reliably transmitting, routing, and synchronizing video and associated data over IP-based networks.
-
E.
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.
- F. None of above. chosen
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.