Triple
T11536896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rec. 2020 |
E273572
|
entity |
| Predicate | definesLumaCoefficients |
P99570
|
FINISHED |
| Object | Y′ from R′G′B′ |
—
|
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: Y′ from R′G′B′ | Statement: [Rec. 2020, definesLumaCoefficients, Y′ from R′G′B′]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesLumaCoefficients Context triple: [Rec. 2020, definesLumaCoefficients, Y′ from R′G′B′]
-
A.
luminanceRange
Indicates the span between the minimum and maximum luminance (brightness) values associated with an entity or visual element.
-
B.
relativeLuminance
Indicates the measured brightness of one entity relative to a reference or to other entities in the same context.
-
C.
chromaticityCoordinatesStandard
Indicates the standard or reference system used to define the chromaticity coordinates associated with a color measurement or representation.
-
D.
designLuminosity
Indicates the specified luminosity level or brightness characteristics that something is designed or intended to have.
-
E.
colorEncoding
Indicates how the color information of an entity is represented, formatted, or encoded.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8839cdf688190ae75c0e6fece8e33 |
completed | April 10, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d8279925e4819089210611c0d8e61a |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 8, 2026, 9:37 p.m.