Triple
T8483272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OS/390 |
E200569
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mainframe operating system |
C24492
|
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 operating system Context triple: [OS/390, instanceOf, mainframe operating system]
-
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.
microcomputer operating system
A microcomputer operating system is software that manages a small computer’s hardware resources and provides essential services for running application programs and user interactions.
-
C.
time-sharing system
A time-sharing system is an operating system that allows multiple users or processes to share computing resources concurrently by rapidly switching the CPU among them, giving the illusion of simultaneous execution.
-
D.
multiuser operating system
A multiuser operating system is a software environment that allows multiple users to access and use a computer system's resources simultaneously and independently, typically through separate user accounts and sessions.
-
E.
multitasking operating system
A multitasking operating system is software that manages computer hardware and resources to run multiple processes or applications seemingly simultaneously by rapidly switching the CPU among them and coordinating their execution.
- 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:12 p.m.