Triple
T31946175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R1 button |
E815656
|
entity |
| Predicate | controllerFamily |
P11218
|
FINISHED |
| Object | DualShock |
—
|
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: DualShock | Statement: [R1 button, controllerFamily, DualShock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controllerFamily Context triple: [R1 button, controllerFamily, DualShock]
-
A.
productFamily
chosen
Indicates that one product belongs to, or is categorized under, a broader product family or line.
-
B.
kernelFamily
Indicates that one kernel is a member of, or derived from, a particular family or class of related kernels.
-
C.
frameworkFamily
Indicates that one framework belongs to the same overarching family or lineage as another framework, typically sharing core principles, architecture, or origin.
-
D.
serviceDesignationFamily
Indicates that one service designation is part of the same family or grouping as another, reflecting a shared classification or closely related category.
-
E.
controlFamilyExample
Indicates that one entity exercises authority, guidance, or influence over a family or family-related situation as an illustrative or example case.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 1, 2026, 12:06 a.m.