Triple
T37967847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony PSP Graphics Core |
E947195
|
entity |
| Predicate | targetDisplay |
P23550
|
FINISHED |
| Object | PSP LCD screen |
—
|
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: PSP LCD screen | Statement: [Sony PSP Graphics Core, targetDisplay, PSP LCD screen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetDisplay Context triple: [Sony PSP Graphics Core, targetDisplay, PSP LCD screen]
-
A.
targetSurface
Indicates the surface or area that an action, effect, or object is directed at or intended to impact.
-
B.
displays
chosen
Indicates that one entity visually presents or shows another entity’s content or information.
-
C.
integratedDisplay
Indicates that a display is built into and forms a unified part of another device or system, rather than being a separate external unit.
-
D.
targetsShow
Indicates that one entity is the intended audience or focus of a particular show or presentation.
-
E.
displayController
Indicates a relationship where one entity manages or controls the visual output or presentation of information on a display device for another entity.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff4de66ba481908e7184b3cf9d4d2d |
completed | May 9, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69ff4c702a5881909c6684c74807e945 |
completed | May 9, 2026, 3:02 p.m. |
Created at: May 3, 2026, 4:20 p.m.