Triple
T8570857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Control Program for Microcomputers |
E202920
|
entity |
| Predicate | primaryStorageMedium |
P9901
|
FINISHED |
| Object | floppy disk |
—
|
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: floppy disk | Statement: [Control Program for Microcomputers, primaryStorageMedium, floppy disk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStorageMedium Context triple: [Control Program for Microcomputers, primaryStorageMedium, floppy disk]
-
A.
secondaryStorage
Indicates that an entity serves as a secondary (non-primary) storage location or medium for another entity’s data or resources.
-
B.
hasPhysicalMedium
Indicates that one entity serves as the tangible carrier or material form through which another entity exists, is stored, or is transmitted.
-
C.
primaryMemoryType
chosen
Indicates the main or dominant type of memory associated with or used by an entity in a given context.
-
D.
primaryMedium
Indicates the main material, format, or channel through which something is created, expressed, or communicated.
-
E.
storageTechnology
Indicates the type or method of data storage technology used or associated with an 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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea4223888190a56d9026ae0b9ec0 |
completed | March 31, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:21 p.m.