Triple
T13556886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HDR10 |
E323797
|
entity |
| Predicate | minimumBitDepth |
P30796
|
FINISHED |
| Object | 10-bit per color channel |
—
|
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 per color channel | Statement: [HDR10, minimumBitDepth, 10-bit per color channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumBitDepth Context triple: [HDR10, minimumBitDepth, 10-bit per color channel]
-
A.
minimumDepth
Indicates the smallest or shallowest depth value associated with an entity or between entities in a given context.
-
B.
colorDepth
chosen
Indicates the bit-depth used to represent the color information of an image or display, defining how many distinct colors can be shown.
-
C.
minimumHeatPerBit
Indicates the least amount of heat that must be generated or dissipated for each unit of information (bit) processed or transmitted in a given context.
-
D.
bitWidth
Indicates the number of bits used to represent or encode a given value, type, or data element.
-
E.
minimumDegree
Indicates that the relationship specifies the smallest number of connections or edges incident to any entity within a given structure or set.
- 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.