Triple
T21207042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo DSi |
E522613
|
entity |
| Predicate | touchScreen |
P62733
|
FINISHED |
| Object | resistive touch screen on bottom display |
—
|
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: resistive touch screen on bottom display | Statement: [Nintendo DSi, touchScreen, resistive touch screen on bottom display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touchScreen Context triple: [Nintendo DSi, touchScreen, resistive touch screen on bottom display]
-
A.
touchscreenType
chosen
Indicates the specific kind or technology of touchscreen associated with an entity.
-
B.
touchesState
Indicates that one entity is in physical contact with, or directly affects, the state or condition of another entity.
-
C.
hasTouchControls
Indicates that an entity supports or is operated through touch-based input controls.
-
D.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
-
E.
hasTouchCoverCompatibility
Indicates that one entity is compatible for use with a specific touch cover accessory associated with 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73435322c8190bf4156fbd14edc5c |
completed | April 21, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:24 p.m.