Triple
T21644285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPC664 |
E534174
|
entity |
| Predicate | storageCapacityPerDisk |
P145361
|
FINISHED |
| Object | approximately 180 KB per side |
—
|
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 180 KB per side | Statement: [CPC664, storageCapacityPerDisk, approximately 180 KB per side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storageCapacityPerDisk Context triple: [CPC664, storageCapacityPerDisk, approximately 180 KB per side]
-
A.
storageCapacity
Indicates the maximum amount of data or material that a storage entity can hold.
-
B.
dataCapacity
Indicates the maximum amount of data that something can store, handle, or transmit.
-
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.
installedCapacityUnit
Indicates the unit of measurement used to express the installed capacity associated with an entity.
-
E.
dataCapacityDigits
Indicates the number of decimal digits used to represent or specify a data capacity value.
- 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef5393ed388190a0bc385de2b861bf |
completed | April 27, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:35 p.m.