Triple
T37949336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlayStation Move navigation controller |
E946696
|
entity |
| Predicate | hasButtonLayout |
P5738
|
FINISHED |
| Object | PlayStation face buttons |
—
|
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 face buttons | Statement: [PlayStation Move navigation controller, hasButtonLayout, PlayStation face buttons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasButtonLayout Context triple: [PlayStation Move navigation controller, hasButtonLayout, PlayStation face buttons]
-
A.
hasButtons
Indicates that an entity possesses one or more buttons as part of its features or design.
-
B.
hasLayout
Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of another entity.
-
C.
hasLayoutElement
Indicates that one entity includes, contains, or is associated with a specific layout element as part of its structural or visual arrangement.
-
D.
hasKeypadLayout
chosen
Indicates that one entity possesses or uses a specific arrangement or configuration of keys or buttons provided by another entity.
-
E.
hasStandardLayout
Indicates that an entity follows a predefined or commonly accepted arrangement or structure.
- 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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:20 p.m.