Triple
T37164393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVB-GSE |
E920755
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | DVB protocol |
C30031
|
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: DVB protocol Context triple: [DVB-GSE, instanceOf, DVB protocol]
-
A.
digital broadcasting standard family
chosen
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.
virtual multichannel video programming distributor
A virtual multichannel video programming distributor is an online service that delivers multiple live television channels and related video content over the internet without owning traditional physical transmission infrastructure like cable or satellite systems.
-
C.
Audio Video Bridging protocol
Audio Video Bridging protocol is a set of IEEE Ethernet standards that provide time-synchronized, low-latency, and reliable transport of audio and video streams over local area networks.
-
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.
broadcast television standard
A broadcast television standard is a defined set of technical specifications and protocols that govern how video and audio signals are encoded, transmitted, and received for over-the-air television broadcasting.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.