Triple

T1817785
Position Surface form Disambiguated ID Type / Status
Subject IBM i E40472 entity
Predicate successorTo P78 FINISHED
Object AS/400 operating system family E40472 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: AS/400 operating system family | Statement: [IBM i, successorTo, AS/400 operating system family]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: AS/400 operating system family
Context triple: [IBM i, successorTo, AS/400 operating system family]
  • A. IBM i chosen
    IBM i is IBM’s integrated operating system for its Power Systems servers, known for its built-in database, high reliability, and strong support for enterprise applications.
  • B. OS/390
    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.
  • C. z/OS
    z/OS is IBM’s 64-bit mainframe operating system designed for high-volume, secure, and reliable enterprise computing workloads.
  • D. AIX
    AIX is IBM’s proprietary Unix operating system designed for enterprise servers and high-reliability, scalable computing environments.
  • E. 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.
  • 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_69a8864526c081908a3a4d74f689e2c5 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa65f7b84081909005ce36ef1199db completed March 6, 2026, 5:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69add1bd5f68819080a4fe06e3e1f76d completed March 8, 2026, 7:45 p.m.
Created at: March 4, 2026, 7:32 p.m.