Triple
T6789738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JPEG |
E155901
|
entity |
| Predicate | commonlyUsedColorSubsampling |
P73007
|
FINISHED |
| Object | 4:2:0 |
—
|
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: 4:2:0 | Statement: [JPEG, commonlyUsedColorSubsampling, 4:2:0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyUsedColorSubsampling Context triple: [JPEG, commonlyUsedColorSubsampling, 4:2:0]
-
A.
supportsColorSampling
Indicates that one entity can perform or accommodate color sampling operations on another entity or its data.
-
B.
colorEncoding
Indicates how the color information of an entity is represented, formatted, or encoded.
-
C.
colorEncodingMethod
Indicates the method or scheme used to represent or encode color information.
-
D.
colorSystemCompatibleWith
Indicates that one color system can be accurately used, interpreted, or converted within the context of another color system without loss of intended color meaning.
-
E.
colorImaging
Indicates a relationship where an entity captures, processes, or represents visual information specifically in terms of color.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2ab4ce88190b6311e4d5aac758c |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1b0d2a48190b249dcc671b9b5e4 |
completed | March 27, 2026, 6:51 p.m. |
Created at: March 27, 2026, 2:15 p.m.