Triple
T3580040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mario Kart Wii |
E75777
|
entity |
| Predicate | usesControllerFeature |
P39814
|
FINISHED |
| Object | motion controls |
—
|
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: motion controls | Statement: [Mario Kart Wii, usesControllerFeature, motion controls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesControllerFeature Context triple: [Mario Kart Wii, usesControllerFeature, motion controls]
-
A.
usesController
chosen
Indicates that one entity operates, manages, or interacts with another entity through a controller component or mechanism.
-
B.
usedCapability
Indicates that an entity employed or exercised a particular capability, skill, or function in performing an action or achieving a result.
-
C.
hasUseCase
Indicates that one entity is employed, applied, or utilized as a solution or method to address a particular need, problem, or scenario associated with another entity.
-
D.
usesDirective
Indicates that one entity applies, references, or relies on a specific directive issued or defined by another entity.
-
E.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
- 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_69ad85d5e3008190bdfe0bacdd1f5a1b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0ffecdc8190bf01c8ba90e3733e |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.