Triple
T10156547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enhanced Graphics Adapter |
E233789
|
entity |
| Predicate | graphicsModeColors |
P92313
|
FINISHED |
| Object | 16 colors |
—
|
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: 16 colors | Statement: [Enhanced Graphics Adapter, graphicsModeColors, 16 colors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphicsModeColors Context triple: [Enhanced Graphics Adapter, graphicsModeColors, 16 colors]
-
A.
graphicsModeColorsAt640x200
Indicates the number or type of colors available when operating in a graphics display mode with a resolution of 640 by 200 pixels.
-
B.
colorDisplay
Indicates that one entity presents, shows, or renders the color associated with another entity.
-
C.
colorSystem
Indicates that one entity is a system or scheme used to define, organize, or represent the colors of another entity.
-
D.
graphicsTheme
Indicates the visual style or design motif that characterizes how something is graphically presented or themed.
-
E.
hasColorModel
Indicates that an entity uses or is associated with a particular color representation model (such as RGB, CMYK, or HSV) for defining its colors.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec3c47dc81909679903e6024eb49 |
completed | April 2, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8f869c8190a82ad040993e0244 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9:09 p.m.