Triple
T30483787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMPTE ST 2094 |
E775658
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | video standard family |
C10956
|
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: video standard family Context triple: [SMPTE ST 2094, instanceOf, video standard family]
-
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 compression standard
chosen
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.
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.
-
E.
videotape format
A videotape format is a standardized specification that defines the physical tape characteristics, recording method, and signal encoding used to capture, store, and play back analog or digital video and audio on magnetic tape.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:13 p.m.