Triple
T37537915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UHDTV2 |
E933254
|
entity |
| Predicate | supportsBitDepthRange |
P205957
|
FINISHED |
| Object | 10 to 12 bits per sample |
—
|
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 to 12 bits per sample | Statement: [UHDTV2, supportsBitDepthRange, 10 to 12 bits per sample]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBitDepthRange Context triple: [UHDTV2, supportsBitDepthRange, 10 to 12 bits per sample]
-
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.
typicalBitDepth
Indicates the usual or standard number of bits used to represent each sample or value in a given digital signal or data format.
-
D.
colorDepth
Indicates the bit-depth used to represent the color information of an image or display, defining how many distinct colors can be shown.
-
E.
videoBitDepthInternal
Indicates the number of bits used internally to represent each color component of video data during processing or storage.
- F. None of above. chosen
Provenance (4 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.