Triple
T3636104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twiggy floppy drive |
E77070
|
entity |
| Predicate | capacityPerDisk |
P16219
|
FINISHED |
| Object | approximately 871 KB |
—
|
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: approximately 871 KB | Statement: [Twiggy floppy drive, capacityPerDisk, approximately 871 KB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capacityPerDisk Context triple: [Twiggy floppy drive, capacityPerDisk, approximately 871 KB]
-
A.
installedCapacity
Indicates the maximum output or production capability that has been set up or built for a system, facility, or equipment, typically measured under specified conditions.
-
B.
dataCapacityDigits
Indicates the number of decimal digits used to represent or specify a data capacity value.
-
C.
initialHardDriveCapacity
Indicates the original storage capacity of a hard drive at the time it was first provided, installed, or configured.
-
D.
floppyDriveCapacity
chosen
Indicates the storage capacity associated with a floppy drive.
-
E.
minStorageCapacity
Indicates the minimum storage capacity required, allowed, or guaranteed in a given context or relationship.
- 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_69ad85dd0be48190b738990cb20c4731 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3278bb8819098bbeac023410111 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb842be7c8190b7dfdb7c906f294c |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.