Triple

T7894654
Position Surface form Disambiguated ID Type / Status
Subject VAX E183315 entity
Predicate hasModel P2390 FINISHED
Object VAX-11/730 E183315 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: VAX-11/730 | Statement: [VAX, hasModel, VAX-11/730]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: VAX-11/730
Context triple: [VAX, hasModel, VAX-11/730]
  • A. VAX chosen
    VAX is a line of 32-bit minicomputers and their associated architecture developed by Digital Equipment Corporation, widely used in the late 20th century for time-sharing and scientific computing.
  • B. IBM 5153
    The IBM 5153 is a color CRT monitor designed for use with early IBM PC systems, particularly the IBM PC/XT and PC/AT, supporting CGA graphics.
  • C. Honeywell 316 minicomputer
    The Honeywell 316 minicomputer was a small, 16-bit general-purpose computer from the late 1960s widely used in early networking and control applications.
  • D. DECsystem-10
    The DECsystem-10 was a family of influential 36-bit mainframe computers introduced in the 1960s, widely used in universities and research institutions for time-sharing and early networked computing.
  • E. IBM 3083
    The IBM 3083 is a mainframe computer model in IBM’s 308X family, introduced in the early 1980s as a more powerful and efficient successor to earlier System/370 processors.
  • 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_69ca828c474c8190a254d6499871eaff completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a15a7e88190a05474844817e5d2 completed March 31, 2026, 3:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc562c6e188190adbdf99479170920 completed March 31, 2026, 11:18 p.m.
Created at: March 30, 2026, 5:01 p.m.