Triple
T11658433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raspberry Pi |
E277066
|
entity |
| Predicate | usesStorageMedium |
P88577
|
FINISHED |
| Object | microSD 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: microSD card | Statement: [Raspberry Pi, usesStorageMedium, microSD card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStorageMedium Context triple: [Raspberry Pi, usesStorageMedium, microSD card]
-
A.
hasPhysicalMedium
Indicates that one entity serves as the tangible carrier or material form through which another entity exists, is stored, or is transmitted.
-
B.
storageDevice
chosen
Indicates a relationship where one entity functions as a device used to store data or digital information for another entity.
-
C.
usedMedium
Indicates that an action or communication was carried out through a particular medium or channel.
-
D.
supportsPhysicalMedia
Indicates that one entity provides the capability to use, read, or handle physical media formats (such as discs, tapes, or printed materials) associated with another entity.
-
E.
hasStorage
Indicates that one entity provides or contains storage capacity or space for another entity or resource.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.