Triple
T8993267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM 3033 |
E214840
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mainframe computer |
C25416
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: mainframe computer Context triple: [IBM 3033, instanceOf, mainframe computer]
-
A.
mainframe computer series
A mainframe computer series is a family of high-performance, large-scale computers designed for reliable, centralized processing of massive workloads and critical enterprise applications over multiple generations.
-
B.
mainframe operating system
A mainframe operating system is a highly reliable, secure, and scalable software platform designed to manage and coordinate the intensive processing, massive I/O, and concurrent workloads of large enterprise mainframe computers.
-
C.
electronic stored-program computer
An electronic stored-program computer is a digital machine that executes instructions and processes data by electronically manipulating binary information according to programs held in its memory.
-
D.
minicomputer manufacturer
A minicomputer manufacturer is a company that designs, produces, and sells mid-sized computers that offer greater processing power than microcomputers but are smaller and less expensive than mainframes, typically serving business, scientific, or industrial applications.
-
E.
stored-program computer
A stored-program computer is a computing system in which both program instructions and data are stored in the same read-write memory, allowing the machine to modify and execute instructions sequentially or conditionally.
- F. None of above. chosen
Provenance (1 batch)
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_69ca83a05c608190bdfdbdb25e994b39 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:04 p.m.