Triple
T4093931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IAS machine |
E87767
|
entity |
| Predicate | storageCapacity |
P52985
|
FINISHED |
| Object | 40960 bits |
—
|
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: 40960 bits | Statement: [IAS machine, storageCapacity, 40960 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storageCapacity Context triple: [IAS machine, storageCapacity, 40960 bits]
-
A.
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.
-
B.
dataCapacityDigits
Indicates the number of decimal digits used to represent or specify a data capacity value.
-
C.
capacityCategory
Indicates the classification of something based on the amount or volume it can hold, handle, or accommodate.
-
D.
minStorageCapacity
Indicates the minimum storage capacity required, allowed, or guaranteed in a given context or relationship.
-
E.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefcda2f408190bcf2b64535193162 |
completed | March 9, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef9b34dec81909bbc3def9decc71a |
completed | March 9, 2026, 4:47 p.m. |
Created at: March 9, 2026, 3:40 p.m.