Triple
T37660634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PCH-1000 |
E937709
|
entity |
| Predicate | hasControlInputs |
P74469
|
FINISHED |
| Object | dual analog sticks |
—
|
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: dual analog sticks | Statement: [PCH-1000, hasControlInputs, dual analog sticks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControlInputs Context triple: [PCH-1000, hasControlInputs, dual analog sticks]
-
A.
hasSimpleControls
Indicates that an entity possesses controls or mechanisms that are easy to understand and operate.
-
B.
hasControlElement
Indicates that one entity includes or is associated with a component specifically intended to control, regulate, or influence its behavior or operation.
-
C.
supportsControllerInput
chosen
Indicates that an entity is capable of receiving and handling input from a controller device.
-
D.
requiresControlInput
Indicates that an entity cannot function or proceed autonomously and instead depends on receiving control commands or input from another agent or system.
-
E.
hasManualControls
Indicates that an entity is equipped with controls intended to be operated directly by a human user.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.