Triple
T9030237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMPTE ST 2084 |
E216149
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electro‑optical transfer function 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: electro‑optical transfer function standard Context triple: [SMPTE ST 2084, instanceOf, electro‑optical transfer function standard]
-
A.
IP video transport standard
An IP video transport standard defines the protocols, formats, and procedures for reliably transmitting, routing, and synchronizing video and associated data over IP-based networks.
-
B.
IEEE standard
An IEEE standard is a formally documented set of technical specifications and guidelines developed and maintained by the Institute of Electrical and Electronics Engineers to ensure interoperability, safety, and quality across electrical, electronic, and computing technologies.
-
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.
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.
-
E.
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.
- 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.