Triple
T37164309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVB-CI |
E920753
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Digital Video Broadcasting interface standard |
C63644
|
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 Video Broadcasting interface standard Context triple: [DVB-CI, instanceOf, Digital Video Broadcasting interface standard]
-
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.
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.
-
C.
video standard
chosen
A video standard is a defined set of technical specifications and protocols that govern how video signals are encoded, transmitted, stored, and displayed to ensure compatibility across devices and systems.
-
D.
digital audio-video interface
A digital audio-video interface is a standardized connection system that transmits high-quality digital audio and video signals between electronic devices.
-
E.
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.
- 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.