Triple
T30370006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ST 2084 |
E772521
|
entity |
| Predicate | definesLuminanceRangeFrom |
P85778
|
FINISHED |
| Object | 0 cd/m² |
—
|
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 cd/m² | Statement: [ST 2084, definesLuminanceRangeFrom, 0 cd/m²]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesLuminanceRangeFrom Context triple: [ST 2084, definesLuminanceRangeFrom, 0 cd/m²]
-
A.
luminanceRange
chosen
Indicates the span between the minimum and maximum luminance (brightness) values associated with an entity or visual element.
-
B.
definesLumaCoefficients
Indicates that one entity specifies the numerical coefficients used to compute luma (perceived brightness) from color components for another entity.
-
C.
brightnessRangeClass
Indicates the classification of an entity based on the range or interval of its brightness values.
-
D.
relativeLuminance
Indicates the measured brightness of one entity relative to a reference or to other entities in the same context.
-
E.
designLuminosity
Indicates the specified luminosity level or brightness characteristics that something is designed or intended to have.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 29, 2026, 7:59 p.m.