Triple
T9030238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMPTE ST 2084 |
E216149
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high‑dynamic‑range video standard |
C12076
|
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: high‑dynamic‑range video standard Context triple: [SMPTE ST 2084, instanceOf, high‑dynamic‑range video standard]
-
A.
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.
-
B.
MPEG-4 AVC
MPEG-4 AVC (also known as H.264) is a video compression standard that efficiently encodes digital video for storage and transmission while maintaining high visual quality at relatively low bitrates.
-
C.
high-dynamic-range imaging technology
chosen
High-dynamic-range imaging technology is a method of capturing, processing, and displaying images with a wider range of luminance and color than standard imaging, preserving detail in both very bright and very dark areas.
-
D.
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.
-
E.
high-definition television feed
A high-definition television feed is a digital video and audio signal that delivers television content at significantly higher resolution and clarity than standard-definition broadcasts.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:08 p.m.