Triple
T30369887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perceptual Quantizer |
E772519
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-dynamic-range 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 standard Context triple: [Perceptual Quantizer, instanceOf, high-dynamic-range standard]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
image acquisition standard
An image acquisition standard is a defined set of rules and protocols that ensure consistent, interoperable, and high-quality capture of images across different devices, systems, and workflows.
-
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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:59 p.m.