Triple

T16921914
Position Surface form Disambiguated ID Type / Status
Subject RAD6000 E410461 entity
Predicate operatingSystemSupport P1593 FINISHED
Object VxWorks E198685 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: VxWorks | Statement: [RAD6000, operatingSystemSupport, VxWorks]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: VxWorks
Context triple: [RAD6000, operatingSystemSupport, VxWorks]
  • A. VxWorks chosen
    VxWorks is a real-time operating system (RTOS) widely used in embedded systems across industries such as aerospace, defense, telecommunications, and industrial automation.
  • B. LynxOS
    LynxOS is a real-time, POSIX-compliant operating system designed for embedded and mission-critical applications, particularly in aerospace, defense, and industrial systems.
  • C. QNX
    QNX is a commercial, real-time, microkernel-based operating system widely used in embedded and safety-critical applications such as automotive, industrial, and medical systems.
  • D. QNX Momentics development suite
    QNX Momentics development suite is an integrated development environment and toolchain designed for building, debugging, and optimizing applications for the QNX real-time operating system.
  • E. OS-9
    OS-9 is a real-time, multitasking operating system originally developed by Microware for embedded and industrial computing platforms.
  • 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_69d886c7b1e481908c3766dfa8c13458 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3cdef7df881908b69aa3c4f50ef94 completed April 18, 2026, 6:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00cfd3c488819089e3791c7e704baf completed May 10, 2026, 6:34 p.m.
Created at: April 10, 2026, 5:30 a.m.