Triple
T1774681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commodore Amiga 1000 |
E38950
|
entity |
| Predicate | primaryStorage |
P8611
|
FINISHED |
| Object | 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: 3.5-inch floppy disk drive | Statement: [Commodore Amiga 1000, primaryStorage, 3.5-inch floppy disk drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStorage Context triple: [Commodore Amiga 1000, primaryStorage, 3.5-inch floppy disk drive]
-
A.
primaryMemoryType
Indicates the main or dominant type of memory associated with or used by an entity in a given context.
-
B.
storageOption
chosen
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
-
C.
dataStorage
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
D.
primaryFile
Indicates that one file in a set is designated as the main or most important file associated with a given entity or context.
-
E.
primaryStation
Indicates that one station is designated as the main or principal station associated with another entity or within a given context.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab17e368048190b7b73d156400f772 |
completed | March 6, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69aa61cd4c1c8190a8dff391f5642bfe |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.