Triple
T35594251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh Performa 5300 series |
E1028582
|
entity |
| Predicate | defaultHardDiskSizeRange |
P40530
|
FINISHED |
| Object | 500–1000 MB |
—
|
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: 500–1000 MB | Statement: [Macintosh Performa 5300 series, defaultHardDiskSizeRange, 500–1000 MB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultHardDiskSizeRange Context triple: [Macintosh Performa 5300 series, defaultHardDiskSizeRange, 500–1000 MB]
-
A.
standardHardDiskCapacity
Indicates the typical or nominal storage capacity of a hard disk as defined by a given standard or specification.
-
B.
initialHardDriveCapacity
chosen
Indicates the original storage capacity of a hard drive at the time it was first provided, installed, or configured.
-
C.
recommendedMinimumSize
Indicates the smallest size that is advised or suggested as a minimum for something to be used or considered appropriate.
-
D.
maximumVolumeSize
Indicates the largest allowable size or capacity that a volume can have within a given system or context.
-
E.
typicalRAMRange
Indicates the usual or commonly expected range of RAM capacity associated with an 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:05 p.m.