Triple
T24928455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PNG |
E618924
|
entity |
| Predicate | supportsAlphaBitDepth |
P164965
|
FINISHED |
| Object | 8-bit alpha |
—
|
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: 8-bit alpha | Statement: [PNG, supportsAlphaBitDepth, 8-bit alpha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAlphaBitDepth Context triple: [PNG, supportsAlphaBitDepth, 8-bit alpha]
-
A.
hasAlphaEnhancement
Indicates that an entity possesses an increased or augmented alpha-related property, characteristic, or capability compared to a baseline.
-
B.
colorDepth
Indicates the bit-depth used to represent the color information of an image or display, defining how many distinct colors can be shown.
-
C.
supportsColorSampling
Indicates that one entity can perform or accommodate color sampling operations on another entity or its data.
-
D.
supportsInterlacing
Indicates that one entity is capable of handling or enabling interlaced data or processing for another entity.
-
E.
supportsColorProfile
Indicates that one entity is capable of recognizing, handling, or applying the specified color profile associated with another entity.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 18, 2026, 5:29 a.m.