Triple
T8814993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Classic Controller |
E209755
|
entity |
| Predicate | providesControlScheme |
P74469
|
FINISHED |
| Object | traditional control scheme |
—
|
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: traditional control scheme | Statement: [Classic Controller, providesControlScheme, traditional control scheme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesControlScheme Context triple: [Classic Controller, providesControlScheme, traditional control scheme]
-
A.
supportsControllerInput
chosen
Indicates that an entity is capable of receiving and handling input from a controller device.
-
B.
hasMotionControls
Indicates that an entity supports or involves control through physical movement or gestures rather than (or in addition to) traditional input methods.
-
C.
supportsGameCubeControllers
Indicates that an entity is compatible with and can be used with GameCube controllers.
-
D.
hasTouchControls
Indicates that an entity supports or is operated through touch-based input controls.
-
E.
hasControlElement
Indicates that one entity includes or is associated with a component specifically intended to control, regulate, or influence its behavior or operation.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff2ff248190bafcafe8b3860e53 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.