Triple
T29101519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega Mega Jet |
E736649
|
entity |
| Predicate | controllerButtons |
P92562
|
FINISHED |
| Object | D-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: D-pad | Statement: [Sega Mega Jet, controllerButtons, D-pad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controllerButtons Context triple: [Sega Mega Jet, controllerButtons, D-pad]
-
A.
hasFaceButtons
Indicates that an object or device includes one or more interactive buttons located on its front-facing surface.
-
B.
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.
-
C.
controllerShape
Indicates that one entity has the specified geometric or physical form used as a controller in an interaction or system.
-
D.
hasButtons
chosen
Indicates that an entity possesses one or more buttons as part of its features or design.
-
E.
controlsType
Indicates that one entity has authority over, or the ability to direct or regulate, the type or category of 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 28, 2026, 11:12 a.m.