Triple
T13556887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HDR10 |
E323797
|
entity |
| Predicate | colorSubsamplingSupport |
P99569
|
FINISHED |
| Object | 4:2:0 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 4:2:0 | Statement: [HDR10, colorSubsamplingSupport, 4:2:0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colorSubsamplingSupport Context triple: [HDR10, colorSubsamplingSupport, 4:2:0]
-
A.
chromaSubsamplingOptions
chosen
Indicates how color information is reduced or sampled relative to luminance in an image or video signal.
-
B.
commonlyUsedColorSubsampling
Indicates that a particular color subsampling scheme is frequently or typically used in practice.
-
C.
supportsColorSampling
Indicates that one entity can perform or accommodate color sampling operations on another entity or its data.
-
D.
supportsInterlacedCompositeArtifacts
Indicates that one entity provides compatibility with or functionality for handling interlaced composite artifacts associated with another entity.
-
E.
supportsNonInterlacedModes
Indicates that an entity is capable of handling or operating with non-interlaced (progressive) display modes.
- F. None of above.
Provenance (3 batches)
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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae13bec4819084c1770638c00ed9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:47 p.m.