Triple
T8993292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM 3033 |
E214840
|
entity |
| Predicate | operatingSystem |
P1593
|
FINISHED |
| Object | VM/370 |
E244635
|
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: VM/370 | Statement: [IBM 3033, operatingSystem, VM/370]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VM/370 Context triple: [IBM 3033, operatingSystem, VM/370]
-
A.
VM/370
chosen
VM/370 is IBM's pioneering virtual machine operating system that allowed multiple independent OS environments to run concurrently on System/370 mainframe hardware.
-
B.
IBM System/370
IBM System/370 is a family of IBM mainframe computers introduced in the 1970s that extended and modernized the System/360 architecture while maintaining backward compatibility.
-
C.
IBM System/360
IBM System/360 is a landmark family of mainframe computers introduced in the 1960s that standardized computer architecture and revolutionized business and scientific computing.
-
D.
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.
-
E.
IBM VSE
IBM VSE is an IBM mainframe operating system designed for smaller and midrange systems, focused on batch and transaction processing in business environments.
- 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_69ca83a05c608190bdfdbdb25e994b39 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6876583081909d936dc3c3152587 |
completed | April 1, 2026, 12:36 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0c6d4a5d08190832f41dd9dc82f41 |
completed | April 4, 2026, 8:07 a.m. |
Created at: March 30, 2026, 7:04 p.m.