Triple
T29364229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega Control Stick |
E744671
|
entity |
| Predicate | directionalInputs |
P29448
|
FINISHED |
| Object | 8-way digital directions |
—
|
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: 8-way digital directions | Statement: [Sega Control Stick, directionalInputs, 8-way digital directions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionalInputs Context triple: [Sega Control Stick, directionalInputs, 8-way digital directions]
-
A.
controlDirection
Indicates that one entity exerts influence or guidance over the orientation, course, or movement direction of another entity.
-
B.
movementDirection
Indicates the direction or path along which an entity moves or is moving relative to a reference frame or point.
-
C.
directionalRole
Indicates a role or function defined in terms of a direction or orientation relative to another entity or reference frame.
-
D.
directionalConfiguration
chosen
Indicates a specific spatial or directional arrangement that one entity has relative to another.
-
E.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 28, 2026, 2:21 p.m.