Triple
T30428603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mac Pro (2019) |
E774098
|
entity |
| Predicate | maxConfiguredStorage |
P52985
|
FINISHED |
| Object | 8 TB SSD |
—
|
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: 8 TB SSD | Statement: [Mac Pro (2019), maxConfiguredStorage, 8 TB SSD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxConfiguredStorage Context triple: [Mac Pro (2019), maxConfiguredStorage, 8 TB SSD]
-
A.
maximumVolumeSize
Indicates the largest allowable size or capacity that a volume can have within a given system or context.
-
B.
minStorageCapacity
Indicates the minimum storage capacity required, allowed, or guaranteed in a given context or relationship.
-
C.
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.
-
D.
storageCapacity
chosen
Indicates the maximum amount of data or material that a storage entity can hold.
-
E.
storageCapacityPerDisk
Indicates the amount of data that can be stored on each individual disk.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6866aa9f88190b3e139fb374d6606 |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:06 p.m.