Triple
T37480133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rec. BT.2020 |
E931390
|
entity |
| Predicate | colorGamutType |
P31543
|
FINISHED |
| Object | wide color gamut |
—
|
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: wide color gamut | Statement: [Rec. BT.2020, colorGamutType, wide color gamut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colorGamutType Context triple: [Rec. BT.2020, colorGamutType, wide color gamut]
-
A.
colorGamutRelative
Indicates that one color gamut is defined, measured, or evaluated in relation to another reference gamut rather than in absolute terms.
-
B.
colorPrimaries
Indicates the primary color components or base colors used to define the color representation of an image or visual signal.
-
C.
colourSpaceName
Indicates the specific color space in which a color value or image data is defined or represented.
-
D.
hasWiderGamutThan
Indicates that one entity supports or encompasses a broader range or spectrum (e.g., of colors or values) than another entity.
-
E.
supportsWideColorGamut
chosen
Indicates that one entity provides or enables compatibility with a wide color gamut capability for another entity or context.
- 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_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:17 p.m.