Triple
T21207036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo DSi |
E522613
|
entity |
| Predicate | removableStorage |
P88577
|
FINISHED |
| Object | SD card |
—
|
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: SD card | Statement: [Nintendo DSi, removableStorage, SD card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removableStorage Context triple: [Nintendo DSi, removableStorage, SD card]
-
A.
removable
Indicates that one entity can be detached, taken off, or separated from another without causing damage or permanent alteration.
-
B.
storageDevice
chosen
Indicates a relationship where one entity functions as a device used to store data or digital information for another entity.
-
C.
batteryRemovable
Indicates that the battery of an object or device can be physically removed and replaced by the user or a technician.
-
D.
storageOrgan
Indicates that one entity serves as a storage organ (a specialized structure for storing substances like nutrients or water) for another entity.
-
E.
mechanicalDrive
Indicates a relationship where one entity transmits mechanical power or motion to another, typically via components like gears, belts, or shafts.
- 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.