Triple

T8285616
Position Surface form Disambiguated ID Type / Status
Subject QEMU E193779 entity
Predicate usedWith P4791 FINISHED
Object libvirt E699779 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: libvirt | Statement: [QEMU, usedWith, libvirt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: libvirt
Context triple: [QEMU, usedWith, libvirt]
  • A. Libvirt chosen
    Libvirt is an open-source API, daemon, and management tool for managing platform virtualization technologies such as KVM, QEMU, and Xen.
  • B. oVirt
    oVirt is an open-source virtualization management platform that provides enterprise-grade management of virtual machines, hosts, storage, and networks.
  • C. KubeVirt
    KubeVirt is an open source Kubernetes extension that enables running and managing virtual machine workloads alongside containerized applications on a unified platform.
  • D. QEMU
    QEMU is an open-source machine emulator and virtualizer that enables running operating systems and programs for one hardware platform on another.
  • E. VirtualBox
    VirtualBox is a popular open-source virtualization platform that allows users to run multiple operating systems simultaneously on a single physical machine.
  • 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_69ca82e32db481908b72f3804fa71152 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7ad20ae481908179aba245c73fad completed March 31, 2026, 7:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd688441908190b6b0a39dfb9d87ac completed April 1, 2026, 6:48 p.m.
Created at: March 30, 2026, 5:52 p.m.