Triple
T20949372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo 2DS |
E515938
|
entity |
| Predicate | doesNotSupportDisplayMode |
P74453
|
FINISHED |
| Object | autostereoscopic 3D |
—
|
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: autostereoscopic 3D | Statement: [Nintendo 2DS, doesNotSupportDisplayMode, autostereoscopic 3D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotSupportDisplayMode Context triple: [Nintendo 2DS, doesNotSupportDisplayMode, autostereoscopic 3D]
-
A.
doesNotSupportMode
chosen
Indicates that one entity lacks the capability or compatibility to operate in, or work with, a specified mode associated with another entity.
-
B.
supportsNonInterlacedModes
Indicates that an entity is capable of handling or operating with non-interlaced (progressive) display modes.
-
C.
doNotSupport
Indicates that one entity withholds help, approval, or endorsement from another entity or action.
-
D.
supportsWindowedMode
Indicates that an entity provides or allows operation in a windowed (non-fullscreen) display mode.
-
E.
supportsDisplayResolution
Indicates that one entity is capable of operating with, rendering, or otherwise accommodating the specified display resolution 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_69e0b4fcd678819087a304291f14330a |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fadc08148190b4ff710f94462a26 |
completed | April 21, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 1:15 p.m.