Triple
T20165737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ricoh 2C02 PPU |
E491820
|
entity |
| Predicate | onScreenColors |
P30793
|
FINISHED |
| Object | 25 colors approximately |
—
|
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: 25 colors approximately | Statement: [Ricoh 2C02 PPU, onScreenColors, 25 colors approximately]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onScreenColors Context triple: [Ricoh 2C02 PPU, onScreenColors, 25 colors approximately]
-
A.
maxColorsOnScreen
chosen
Indicates the maximum number of distinct colors that can be displayed on the screen at the same time.
-
B.
onScreenStatus
Indicates that an entity’s current presence or visibility state is being specified relative to a screen or display.
-
C.
hairColorOnScreen
Indicates the hair color that an entity appears to have when shown or rendered on a screen.
-
D.
onScreenDynamicWith
Indicates that two entities are simultaneously visible and interacting or changing together within the same on-screen context.
-
E.
hasScreen
Indicates that an entity is equipped with or includes a screen or display component.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e668442d2c81908bb1a0fac9895b5e |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:35 p.m.