Triple
T37480040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Recommendation ITU-R BT.2020 |
E931388
|
entity |
| Predicate | colourSpaceName |
P188380
|
FINISHED |
| Object | BT.2020 colour space |
—
|
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: BT.2020 colour space | Statement: [Recommendation ITU-R BT.2020, colourSpaceName, BT.2020 colour space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colourSpaceName Context triple: [Recommendation ITU-R BT.2020, colourSpaceName, BT.2020 colour space]
-
A.
colorSystem
Indicates that one entity is a system or scheme used to define, organize, or represent the colors of another entity.
-
B.
coversColorSpace
Indicates that one entity’s color representation range fully includes or spans the color space defined by another entity.
-
C.
colourSystemComponent
Indicates that one entity is a component or part of a colour system associated with another entity.
-
D.
colorDesignationInName
Indicates that a color term is explicitly included as part of an entity’s name or title.
-
E.
colorSystemCompatibleWith
Indicates that one color system can be accurately used, interpreted, or converted within the context of another color system without loss of intended color meaning.
- 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_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. |
| PDg | Predicate description generation | batch_69fba67f78348190ab160988e4698394 |
completed | May 6, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.