Triple
T19450414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atari Lynx |
E486599
|
entity |
| Predicate | controllerInputs |
P74469
|
FINISHED |
| Object | directional pad |
—
|
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: directional pad | Statement: [Atari Lynx, controllerInputs, directional pad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controllerInputs Context triple: [Atari Lynx, controllerInputs, directional pad]
-
A.
controlSurfaces
Indicates that one entity functions as a control surface or set of control surfaces used to influence, steer, or regulate the behavior or state of another entity.
-
B.
supportsControllerInput
chosen
Indicates that an entity is capable of receiving and handling input from a controller device.
-
C.
requiresControlInput
Indicates that an entity cannot function or proceed autonomously and instead depends on receiving control commands or input from another agent or system.
-
D.
controlDirection
Indicates that one entity exerts influence or guidance over the orientation, course, or movement direction of another entity.
-
E.
inputDevice
Indicates that one entity functions as a device used to provide input to another entity or system.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338caeb48190aeb1d511996984e3 |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.