Triple
T29456620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hold-And-Modify 8 |
E747118
|
entity |
| Predicate | supportsPerPixelModificationOf |
P207151
|
FINISHED |
| Object | color components |
—
|
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: color components | Statement: [Hold-And-Modify 8, supportsPerPixelModificationOf, color components]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPerPixelModificationOf Context triple: [Hold-And-Modify 8, supportsPerPixelModificationOf, color components]
-
A.
supportsBitDepthUpTo
Indicates the maximum bit depth value that an entity can handle, process, or is compatible with.
-
B.
supportsInterlacing
Indicates that one entity is capable of handling or enabling interlaced data or processing for another entity.
-
C.
supportsColorSampling
Indicates that one entity can perform or accommodate color sampling operations on another entity or its data.
-
D.
supportsRasterization
Indicates that one entity provides the capability or functionality for another entity to perform rasterization operations.
-
E.
hasPixelPitch
Indicates the distance between adjacent pixels in a display or image sensor, typically measured from center to center.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 28, 2026, 3:46 p.m.