Triple
T37949329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlayStation Move navigation controller |
E946696
|
entity |
| Predicate | worksWithGameConsole |
P192957
|
FINISHED |
| Object | PlayStation 3 Slim |
—
|
NE NERFINISHED |
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: PlayStation 3 Slim | Statement: [PlayStation Move navigation controller, worksWithGameConsole, PlayStation 3 Slim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksWithGameConsole Context triple: [PlayStation Move navigation controller, worksWithGameConsole, PlayStation 3 Slim]
-
A.
hasConsoles
Indicates that one entity possesses, includes, or is equipped with one or more consoles.
-
B.
hasVideoGames
Indicates that one entity possesses, owns, or includes video games in relation to another entity or context.
-
C.
developerOfGameUsed
Indicates that an entity is the developer of a game that is (or was) used or played in a given context.
-
D.
usesGameAs
Indicates that one entity employs or relies on a particular game as a tool, medium, or component to achieve some purpose or function.
-
E.
notableConsoleGame
Indicates that a game is recognized as a significant or prominent title released for a particular video game console.
- 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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69fd328298ac8190b6bd5ded7dca270d |
completed | May 8, 2026, 12:46 a.m. |
Created at: May 3, 2026, 4:20 p.m.