Triple

T8284689
Position Surface form Disambiguated ID Type / Status
Subject IBM System/390 E193760 entity
Predicate operatingSystemSupport P1593 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: [IBM System/390, operatingSystemSupport, OS/390]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: OS/390
Context triple: [IBM System/390, operatingSystemSupport, 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. VM/370
    VM/370 is IBM's pioneering virtual machine operating system that allowed multiple independent OS environments to run concurrently on System/370 mainframe hardware.
  • 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_69ca82e217a48190880695635c44b2ed completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7ad20ae481908179aba245c73fad completed March 31, 2026, 7:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd687e64a08190a45a1cf5f5c32291 completed April 1, 2026, 6:48 p.m.
Created at: March 30, 2026, 5:52 p.m.