Triple
T36190611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HLG (Hybrid Log-Gamma) |
E1046975
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | video 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: video standard Context triple: [HLG (Hybrid Log-Gamma), instanceOf, video standard]
-
A.
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.
-
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.
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.
-
D.
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.
-
E.
high-definition video format
A high-definition video format is a digital video standard that delivers significantly higher resolution, clarity, and detail than standard-definition formats, typically including 720p, 1080p, or higher resolutions.
- F. None of above. chosen
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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.