Triple
T22027016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIE standard illuminant D50 |
E543993
|
entity |
| Predicate | CIE1931xyChromaticity_y |
P66293
|
FINISHED |
| Object | 0.35850 |
—
|
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: 0.35850 | Statement: [CIE standard illuminant D50, CIE1931xyChromaticity_y, 0.35850]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CIE1931xyChromaticity_y Context triple: [CIE standard illuminant D50, CIE1931xyChromaticity_y, 0.35850]
-
A.
hasChromaticityCoordinateY
chosen
Indicates that an entity is associated with a specific Y chromaticity coordinate value in a color space.
-
B.
hasChromaticityCoordinateX
Indicates that an entity has a specified x-coordinate value in a chromaticity color space.
-
C.
bluePrimary_y
Indicates that the entity has blue as its primary color along the y-dimension or vertical axis.
-
D.
chromaticityCoordinatesStandard
Indicates the standard or reference system used to define the chromaticity coordinates associated with a color measurement or representation.
-
E.
hasRelativeTristimulusX
Indicates that one entity has a specified relative tristimulus X value in relation to another entity or color measurement.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127ccc2ec8190a94d69530d00c06c |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:24 p.m.