Triple
T20166158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TurboExpress |
E491828
|
entity |
| Predicate | controllerLayout |
P138218
|
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: [TurboExpress, controllerLayout, D-pad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controllerLayout Context triple: [TurboExpress, controllerLayout, D-pad]
-
A.
controlLayout
Indicates that one entity determines or manages the spatial or structural arrangement of another entity.
-
B.
crewLayout
Indicates how crew members are arranged or distributed within a vehicle, vessel, or structure.
-
C.
controllerShape
chosen
Indicates that one entity has the specified geometric or physical form used as a controller in an interaction or system.
-
D.
layoutSupport
Indicates that one entity provides or enables structural or spatial arrangement capabilities for another entity.
-
E.
basedOnLayout
Indicates that one entity is derived from, structured according to, or determined by the layout or spatial arrangement defined by 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e668442d2c81908bb1a0fac9895b5e |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:35 p.m.