Triple
T12241062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNIVAC I |
E291729
|
entity |
| Predicate | tapeCapacity |
P52985
|
FINISHED |
| Object | about 1.44 megabytes per reel |
—
|
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: about 1.44 megabytes per reel | Statement: [UNIVAC I, tapeCapacity, about 1.44 megabytes per reel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tapeCapacity Context triple: [UNIVAC I, tapeCapacity, about 1.44 megabytes per reel]
-
A.
dataCapacity
Indicates the maximum amount of data that something can store, handle, or transmit.
-
B.
trackCapacity
Indicates the maximum number of trains or amount of traffic that a specific track segment is designed to handle within a given time period.
-
C.
storageCapacity
chosen
Indicates the maximum amount of data or material that a storage entity can hold.
-
D.
ramCapacity
Indicates the amount of system memory (RAM) that an entity possesses or supports.
-
E.
dataCapacityDigits
Indicates the number of decimal digits used to represent or specify a data capacity value.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.