Triple

T1892222
Position Surface form Disambiguated ID Type / Status
Subject IBM RS/6000 E41897 entity
Predicate marketedAs P1395 FINISHED
Object RS/6000 E41897 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: RS/6000 | Statement: [IBM RS/6000, marketedAs, RS/6000]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RS/6000
Context triple: [IBM RS/6000, marketedAs, RS/6000]
  • A. IBM RS/6000 systems chosen
    IBM RS/6000 systems are a family of RISC-based workstations and servers from IBM, widely used in enterprise and technical computing environments for running UNIX (AIX) and high-performance applications.
  • B. 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.
  • C. IBM i
    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.
  • D. 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.
  • E. AIX
    AIX is IBM’s proprietary Unix operating system designed for enterprise servers and high-reliability, scalable computing 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_69a8864b6de0819098d089f6a1b910a7 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb145f96c8190a71bb9e442892e68 completed March 7, 2026, 5:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69adeae9e1f4819082afdd3b8e065c01 completed March 8, 2026, 9:32 p.m.
Created at: March 4, 2026, 7:34 p.m.