Triple
T35759643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burroughs A series |
E1033536
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mainframe computer line |
C11537
|
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 line Context triple: [Burroughs A series, instanceOf, mainframe computer line]
-
A.
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.
-
B.
mainframe computer series
chosen
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.
minicomputer line
A minicomputer line is a series of related mid-sized computer systems designed to offer multi-user processing power and functionality between that of mainframes and microcomputers.
-
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.
IBM mainframe peripheral
An IBM mainframe peripheral is an external hardware device, such as storage units, printers, or communication controllers, designed to connect to and extend the input, output, and processing capabilities of an IBM mainframe computer system.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.