Triple
T28608187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESA/390 |
E724108
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IBM mainframe architecture |
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: IBM mainframe architecture Context triple: [ESA/390, instanceOf, IBM mainframe architecture]
-
A.
mainframe computer
chosen
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
mainframe clustering architecture
A mainframe clustering architecture is a high-availability, scalable configuration in which multiple mainframe systems are interconnected and managed as a single logical resource pool to balance workloads, ensure fault tolerance, and optimize performance.
- F. None of above.
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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:28 a.m.