Triple
T562901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh 128K |
E13491
|
entity |
| Predicate | storage |
P8611
|
FINISHED |
| Object | 400 KB 3.5-inch floppy disk drive |
—
|
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: 400 KB 3.5-inch floppy disk drive | Statement: [Macintosh 128K, storage, 400 KB 3.5-inch floppy disk drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storage Context triple: [Macintosh 128K, storage, 400 KB 3.5-inch floppy disk drive]
-
A.
storageOption
chosen
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
-
B.
dataStorage
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
C.
storageFacility
Indicates a relationship where one entity serves as a place or facility used to store another entity or its items.
-
D.
save
Indicates preserving or storing something from loss, harm, or use, often for future benefit or protection.
-
E.
storesEnergyAs
Indicates that one entity retains or accumulates energy in the form or medium specified 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49a712bc48190ba298b3c76ab11cc |
completed | March 1, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69a494c044648190a98589ab18935216 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.