Triple
T31946211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magma Red |
E815657
|
entity |
| Predicate | controllerModel |
P195822
|
FINISHED |
| Object | DualShock 4 Wireless Controller |
—
|
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 4 Wireless Controller | Statement: [Magma Red, controllerModel, DualShock 4 Wireless Controller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controllerModel Context triple: [Magma Red, controllerModel, DualShock 4 Wireless Controller]
-
A.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
-
B.
controlApp
Indicates that one entity has the ability or authority to operate, manage, or direct the behavior of an application.
-
C.
controlsSystem
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
D.
controlMethods
Indicates the methods or techniques used by one entity to direct, regulate, or influence the behavior, operation, or state of another entity.
-
E.
controllerStyle
Indicates the manner or configuration in which a controller operates or is presented in relation to its associated system or interface.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
| PDg | Predicate description generation | batch_69fde9fb68388190ada4a7018e2a2f76 |
completed | May 8, 2026, 1:49 p.m. |
Created at: May 1, 2026, 12:06 a.m.