Triple
T30363957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM 3350 disk storage |
E772364
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IBM mainframe peripheral |
C56811
|
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: IBM mainframe peripheral Context triple: [IBM 3350 disk storage, instanceOf, IBM mainframe peripheral]
-
A.
IBM 3270 family device
An IBM 3270 family device is a block-oriented terminal or controller used to interact with mainframe systems, optimized for high-speed, low-overhead data entry and display in enterprise environments.
-
B.
mainframe computer
A mainframe computer is a large, powerful, and highly reliable central computer system designed to process vast amounts of data and support numerous simultaneous users and critical applications, typically used by large organizations.
-
C.
IBM mainframe networking technology
IBM mainframe networking technology encompasses the hardware, software, and protocols (such as SNA and VTAM) that enable secure, high-volume, and reliable communication between IBM mainframes and distributed systems.
-
D.
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.
-
E.
mainframe computer manufacturer
A mainframe computer manufacturer is a company that designs, builds, and supports large-scale, high-performance central computers used by enterprises and governments for mission-critical, high-volume data processing.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:58 p.m.