Triple
T37480223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rec. 709 |
E931392
|
entity |
| Predicate | whitePointX |
P66292
|
FINISHED |
| Object | 0.3127 |
—
|
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.3127 | Statement: [Rec. 709, whitePointX, 0.3127]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: whitePointX Context triple: [Rec. 709, whitePointX, 0.3127]
-
A.
whitePoint
Indicates the reference color point or standard white used as a basis for color measurements or calibration in a color space.
-
B.
whitePointCCT
Indicates the correlated color temperature value that defines the white point reference for a color space or imaging system.
-
C.
hasChromaticityCoordinateX
chosen
Indicates that an entity has a specified x-coordinate value in a chromaticity color space.
-
D.
hasRelativeTristimulusX
Indicates that one entity has a specified relative tristimulus X value in relation to another entity or color measurement.
-
E.
chromaticityCoordinatesStandard
Indicates the standard or reference system used to define the chromaticity coordinates associated with a color measurement or representation.
- 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_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.