Triple
T2105909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM PC AT |
E37193
|
entity |
| Predicate | supportedFloppyDrive |
P16219
|
FINISHED |
| Object | 360 KB 5.25-inch floppy 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: 360 KB 5.25-inch floppy drive | Statement: [IBM PC AT, supportedFloppyDrive, 360 KB 5.25-inch floppy drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedFloppyDrive Context triple: [IBM PC AT, supportedFloppyDrive, 360 KB 5.25-inch floppy drive]
-
A.
hasFloppyDrive
Indicates that an entity is equipped with or includes a floppy disk drive.
-
B.
floppyDriveCapacity
chosen
Indicates the storage capacity associated with a floppy drive.
-
C.
floppyDiskFormat
Indicates the specific data storage format or standard used on a floppy disk.
-
D.
supportsInstallationMedia
Indicates that one entity is capable of accepting, handling, or working with a specified type of installation media for setup or deployment purposes.
-
E.
supportsExternalDrive
Indicates that one entity is capable of working with, recognizing, or providing functionality for an external storage drive.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbaddeb148190b728bce7a7b041fb |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.