Triple
T3727831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVB-S |
E78991
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | satellite television 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: satellite television standard Context triple: [DVB-S, instanceOf, satellite television 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.
digital satellite television service
A digital satellite television service is a broadcast system that delivers compressed digital TV and audio channels to subscribers via signals transmitted from satellites to small dish antennas at their premises.
-
D.
broadcast television system
A broadcast television system is an integrated network of equipment, standards, and transmission channels that captures, encodes, and distributes audiovisual content over the air or via cable/satellite to multiple receivers simultaneously.
-
E.
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.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:34 p.m.