Triple
T15217878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modified National Institute of Standards and Technology database |
E363685
|
entity |
| Predicate | pixelValueRange |
P117563
|
FINISHED |
| Object | 0–255 |
—
|
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–255 | Statement: [Modified National Institute of Standards and Technology database, pixelValueRange, 0–255]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pixelValueRange Context triple: [Modified National Institute of Standards and Technology database, pixelValueRange, 0–255]
-
A.
luminanceRange
Indicates the span between the minimum and maximum luminance (brightness) values associated with an entity or visual element.
-
B.
hasColorRange
Indicates that an entity possesses or is associated with a specific span or set of colors, rather than a single discrete color.
-
C.
pixelCount
Indicates the total number of individual pixels that make up a given image or visual element.
-
D.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
E.
pixelArray
Indicates a relationship where an entity is represented or stored as an ordered array of pixel values.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0076f90c481909989befe031a2cae |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:11 a.m.