Triple
T20165750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ricoh 2C02 PPU |
E491820
|
entity |
| Predicate | visibleResolution |
P5732
|
FINISHED |
| Object | 256x240 pixels nominal |
—
|
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: 256x240 pixels nominal | Statement: [Ricoh 2C02 PPU, visibleResolution, 256x240 pixels nominal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibleResolution Context triple: [Ricoh 2C02 PPU, visibleResolution, 256x240 pixels nominal]
-
A.
displayResolution
chosen
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
-
B.
visualDetail
Indicates that one entity provides or specifies the visual characteristics, features, or appearance details of another entity.
-
C.
sensorResolution
Indicates the level of detail or precision with which a sensor can measure or distinguish changes in the observed quantity or environment.
-
D.
mainResolution
Indicates that one resolution is the primary or most important resolution associated with a given context or entity.
-
E.
resolutionOf
Indicates that one entity is the formal decision, outcome, or solution produced in response to, or for the purpose of addressing, another entity such as an issue, proposal, or problem.
- 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.