Triple

T1821682
Position Surface form Disambiguated ID Type / Status
Subject CP/M E40551 entity
Predicate successor P78 FINISHED
Object CP/M-86 E36205 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: CP/M-86 | Statement: [CP/M, successor, CP/M-86]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CP/M-86
Context triple: [CP/M, successor, CP/M-86]
  • A. CP/M-86 chosen
    CP/M-86 is a 16-bit version of the CP/M operating system designed for Intel 8086/8088-based computers, serving as an early alternative to MS-DOS on machines like the IBM PC.
  • B. CP/M
    CP/M is an early microcomputer operating system widely used in the late 1970s and early 1980s, known for its influence on later systems like MS-DOS.
  • C. MS-DOS Executive
    MS-DOS Executive is the simple file management and program-launching shell that served as the primary user interface in early versions of Microsoft Windows, notably Windows 1.0.
  • D. Concurrent CP/M
    Concurrent CP/M is a multiuser, multitasking variant of the CP/M operating system developed by Digital Research for microcomputers.
  • E. Xenix
    Xenix was a Microsoft-licensed, business-oriented version of the Unix operating system that ran on microcomputers in the late 1970s and 1980s.
  • 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_69aa662b910c8190b1746730ee09015a completed March 6, 2026, 5:29 a.m.
NED1 Entity disambiguation (via context triple) batch_69add1bf7b3c81909fd2d548be2baa8f completed March 8, 2026, 7:45 p.m.
Created at: March 4, 2026, 7:32 p.m.