Triple
T8470500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh File System |
E200268
|
entity |
| Predicate | defaultVolumeFormat |
P83488
|
FINISHED |
| Object | 400 KB 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: 400 KB floppy disk | Statement: [Macintosh File System, defaultVolumeFormat, 400 KB floppy disk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultVolumeFormat Context triple: [Macintosh File System, defaultVolumeFormat, 400 KB floppy disk]
-
A.
defaultPackageFormat
Indicates the standard or primary packaging format that is used by default for an item or distribution.
-
B.
primaryDatabaseFormat
Indicates the main data storage format or structure used by a database as its default or principal representation.
-
C.
maximumVolumeSize
Indicates the largest allowable size or capacity that a volume can have within a given system or context.
-
D.
containerFormats
Indicates that one entity serves as a container or packaging format used to hold, encapsulate, or structure the contents of another entity.
-
E.
volume
Indicates the amount of three-dimensional space an entity occupies or contains.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f234c481909534de6fd702f4cf |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:11 p.m.