Triple
T19479535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compaq Armada 3500 series |
E487341
|
entity |
| Predicate | floppyDriveSupport |
P16218
|
FINISHED |
| Object | 3.5-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: 3.5-inch floppy drive | Statement: [Compaq Armada 3500 series, floppyDriveSupport, 3.5-inch floppy drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floppyDriveSupport Context triple: [Compaq Armada 3500 series, floppyDriveSupport, 3.5-inch floppy drive]
-
A.
hasFloppyDrive
chosen
Indicates that an entity is equipped with or includes a floppy disk drive.
-
B.
floppyController
Indicates a relationship where one entity functions as the controller or managing interface for a floppy disk drive associated with another entity.
-
C.
floppyDriveCapacity
Indicates the storage capacity associated with a floppy drive.
-
D.
floppyDiskFormat
Indicates the specific data storage format or standard used on a floppy disk.
-
E.
opticalDrive
Indicates that one entity functions as an optical drive (e.g., CD/DVD/Blu-ray reader/writer) for 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6343882a88190b3cfa65e6cac80d3 |
completed | April 20, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.