Triple
T1096553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sRGB |
E24283
|
entity |
| Predicate | bitDepthTypical |
P4121
|
FINISHED |
| Object | 8 bits per channel |
—
|
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 bits per channel | Statement: [sRGB, bitDepthTypical, 8 bits per channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bitDepthTypical Context triple: [sRGB, bitDepthTypical, 8 bits per channel]
-
A.
bitWidth
chosen
Indicates the number of bits used to represent or encode a given value, type, or data element.
-
B.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
-
C.
typicalPictureFormat
Indicates the standard or most commonly used picture format associated with an entity (such as a device, medium, or context).
-
D.
displayResolution
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
-
E.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b99ffb3481908cd168b6c58e1c6d |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b7448c148190a3c9a4158ebd05b4 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.