Triple
T28023991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master Boot Record |
E707759
|
entity |
| Predicate | maximumAddressableDiskSize |
P12009
|
FINISHED |
| Object | 2 TB with 512-byte sectors |
—
|
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: 2 TB with 512-byte sectors | Statement: [Master Boot Record, maximumAddressableDiskSize, 2 TB with 512-byte sectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumAddressableDiskSize Context triple: [Master Boot Record, maximumAddressableDiskSize, 2 TB with 512-byte sectors]
-
A.
maximumVolumeSize
chosen
Indicates the largest allowable size or capacity that a volume can have within a given system or context.
-
B.
addressSpaceSize
Indicates the total amount of addressable memory or identifier range allocated or available within a given address space.
-
C.
storageCapacityPerDisk
Indicates the amount of data that can be stored on each individual disk.
-
D.
maximumOperatingMach
Indicates the highest machine operating level, capacity, or intensity at which the related entity is allowed or designed to function.
-
E.
standardHardDiskCapacity
Indicates the typical or nominal storage capacity of a hard disk as defined by a given standard or specification.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 8:11 p.m.