Triple
T1835173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | z/OS |
E41049
|
entity |
| Predicate | predecessor |
P97
|
FINISHED |
| Object | OS/390 |
E200569
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: OS/390 | Statement: [z/OS, predecessor, OS/390]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OS/390 Context triple: [z/OS, predecessor, OS/390]
-
A.
OS/390
chosen
OS/390 is an IBM mainframe operating system that evolved from the MVS family, providing robust batch and transaction processing, high reliability, and enterprise-scale workload management.
-
B.
OS/360
OS/360 is IBM's landmark mainframe operating system introduced in the 1960s for the System/360 family, known for pioneering modern concepts in batch processing, multiprogramming, and system software design.
-
C.
z/OS
z/OS is IBM’s 64-bit mainframe operating system designed for high-volume, secure, and reliable enterprise computing workloads.
-
D.
IBM System/390
IBM System/390 is IBM’s family of 1990s mainframe computers that introduced 31-bit ESA/390 architecture and advanced enterprise computing features, forming the basis for later System z systems.
-
E.
IBM System z
IBM System z is IBM’s family of mainframe computers known for high reliability, scalability, and support for enterprise workloads, including running Linux at large scale.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb026aa7c8190bc988d3ee0fd9f41 |
completed | March 7, 2026, 4:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adc9b4b4f08190a0e5ad50de5c0ba8 |
completed | March 8, 2026, 7:10 p.m. |
Created at: March 4, 2026, 7:33 p.m.