Triple
T37480177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UHDTV1 |
E931391
|
entity |
| Predicate | hasLumaBitDepthOptions |
P176344
|
FINISHED |
| Object | 10-bit |
—
|
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: 10-bit | Statement: [UHDTV1, hasLumaBitDepthOptions, 10-bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLumaBitDepthOptions Context triple: [UHDTV1, hasLumaBitDepthOptions, 10-bit]
-
A.
supportsBitDepthUpTo
Indicates the maximum bit depth value that an entity can handle, process, or is compatible with.
-
B.
supportsAlphaBitDepth
Indicates that one entity is capable of handling or providing image or video data with an alpha (transparency) channel at a specified bit depth.
-
C.
videoBitDepthInternal
chosen
Indicates the number of bits used internally to represent each color component of video data during processing or storage.
-
D.
videoBitDepthHDMI
Indicates the number of bits per color component used to represent video data when transmitted over an HDMI connection.
-
E.
chromaSubsamplingOptions
Indicates how color information is reduced or sampled relative to luminance in an image or video signal.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.