Triple

T11306225
Position Surface form Disambiguated ID Type / Status
Subject FICON E267719 entity
Predicate relatedTo P37 FINISHED
Object IBM Z E37331 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: IBM Z | Statement: [FICON, relatedTo, IBM Z]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IBM Z
Context triple: [FICON, relatedTo, IBM Z]
  • A. IBM System z chosen
    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.
  • B. IBM Power Systems
    IBM Power Systems is IBM’s family of high-performance server computers designed for enterprise workloads, known for their reliability, scalability, and support for operating systems like IBM i, AIX, and Linux.
  • C. IBM AT
    The IBM AT (Advanced Technology) is a mid-1980s IBM personal computer that introduced the 80286 processor and became a widely adopted standard for business PCs.
  • D. IBM VM family
    The IBM VM family is a line of IBM mainframe virtualization operating systems designed to run multiple virtual machines and operating environments concurrently on a single physical system.
  • E. 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.
  • 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_69d6aaca5c24819083db46a30d86cb34 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e9a7255c81909675fe9ad6d71934 completed April 9, 2026, 6:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69e50a62ceec8190af25edf44c5fc1e9 completed April 19, 2026, 5:01 p.m.
Created at: April 8, 2026, 9:32 p.m.