Triple
T3453035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVB-T2 |
E72835
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | DVB standard |
C4924
|
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 standard Context triple: [DVB-T2, instanceOf, DVB standard]
-
A.
broadcast television standard
chosen
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.
-
B.
analog television standard
An analog television standard is a technical specification that defines how video and audio signals are encoded, transmitted, and displayed using continuous (non-digital) waveforms for broadcast television.
-
C.
video compression standard
A video compression standard is a defined set of algorithms and rules that specify how digital video is encoded, transmitted, stored, and decoded to reduce file size while maintaining acceptable visual quality.
-
D.
digital terrestrial television platform
A digital terrestrial television platform is a system that delivers multiple digital TV and radio services over terrestrial broadcast frequencies to compatible receivers, often including interactive and on-demand features.
-
E.
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.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:16 p.m.