Triple
T28601787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM 5170 |
E723932
|
entity |
| Predicate | standardFloppyDriveSize |
P173722
|
FINISHED |
| Object | 5.25 inch |
—
|
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: 5.25 inch | Statement: [IBM 5170, standardFloppyDriveSize, 5.25 inch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardFloppyDriveSize Context triple: [IBM 5170, standardFloppyDriveSize, 5.25 inch]
-
A.
floppyDriveCapacity
Indicates the storage capacity associated with a floppy drive.
-
B.
floppyDiskFormat
Indicates the specific data storage format or standard used on a floppy disk.
-
C.
compatibleFloppyDrive
Indicates that one entity can properly use, read from, or write to floppy disks designed for the other entity.
-
D.
floppyDriveModel
Indicates that one entity is a specific model or type designation of a floppy disk drive associated with the other entity.
-
E.
hasFloppyDrive
Indicates that an entity is equipped with or includes a floppy disk drive.
- F. None of above. chosen
Provenance (4 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 28, 2026, 4:25 a.m.