Triple
T11247252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max Steel (video game) |
E266237
|
entity |
| Predicate | hasControlScheme |
P98668
|
FINISHED |
| Object | keyboard and mouse |
—
|
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: keyboard and mouse | Statement: [Max Steel (video game), hasControlScheme, keyboard and mouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControlScheme Context triple: [Max Steel (video game), hasControlScheme, keyboard and mouse]
-
A.
hasMotionControls
Indicates that an entity supports or involves control through physical movement or gestures rather than (or in addition to) traditional input methods.
-
B.
hasTouchControls
Indicates that an entity supports or is operated through touch-based input controls.
-
C.
supportsGameCubeControllers
Indicates that an entity is compatible with and can be used with GameCube controllers.
-
D.
supportsControllerInput
Indicates that an entity is capable of receiving and handling input from a controller device.
-
E.
hasControlCab
Indicates that an entity is equipped with or includes a control cab used for operating or controlling it.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e91d1484819098ee6b2efb5316a5 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d7878906f48190b63ddc103a0c8f9b |
completed | April 9, 2026, 11:03 a.m. |
| PDg | Predicate description generation | batch_69d796cf74308190a5b29d0dd82954a2 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:31 p.m.