Triple
T33203290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VESA DisplayHDR |
E849960
|
entity |
| Predicate | usesColorSpace |
P137834
|
FINISHED |
| Object | DCI‑P3 |
—
|
NE NERFINISHED |
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: DCI‑P3 | Statement: [VESA DisplayHDR, usesColorSpace, DCI‑P3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesColorSpace Context triple: [VESA DisplayHDR, usesColorSpace, DCI‑P3]
-
A.
coversColorSpace
Indicates that one entity’s color representation range fully includes or spans the color space defined by another entity.
-
B.
usesColorSource
Indicates that one entity obtains or applies its color information from another specified source.
-
C.
usesColorMatchingFunctions
Indicates that one entity applies color matching functions to relate or convert color stimuli between different color spaces or representations.
-
D.
isColor
Indicates that one entity represents the color attribute or hue of another entity.
-
E.
supportsColorProfile
chosen
Indicates that one entity is capable of recognizing, handling, or applying the specified color profile associated with another entity.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: May 1, 2026, 1:30 a.m.