Triple
T11705382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DualShock |
E278223
|
entity |
| Predicate | hapticTechnology |
P6774
|
FINISHED |
| Object | rumble motors |
—
|
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: rumble motors | Statement: [DualShock, hapticTechnology, rumble motors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hapticTechnology Context triple: [DualShock, hapticTechnology, rumble motors]
-
A.
headsetHapticsLocation
Indicates the specific physical area or position on a headset where haptic feedback is applied or experienced.
-
B.
technologyInteractedWith
Indicates that an entity has used, engaged with, or otherwise interacted with a particular technology.
-
C.
hasTouchControls
Indicates that an entity supports or is operated through touch-based input controls.
-
D.
technologicalFeature
chosen
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to another entity.
-
E.
supportsVibration
Indicates that one entity provides the capability or functionality to handle, generate, or respond to vibration 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a49c8c38819083d83f5fdec52b7f |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.