Triple

T28611029
Position Surface form Disambiguated ID Type / Status
Subject GNOME Boxes E724167 entity
Predicate supportsVirtualizationBackend P203264 FINISHED
Object libvirt NE NERFINISHED

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: [GNOME Boxes, supportsVirtualizationBackend, libvirt]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsVirtualizationBackend
Context triple: [GNOME Boxes, supportsVirtualizationBackend, libvirt]
  • A. supportsNestedVirtualization
    Indicates that one computing environment or platform enables and correctly handles running virtual machines inside other virtual machines.
  • B. supportsParavirtualization
    Indicates that one entity provides the capability for another entity to run in a paravirtualized environment or to use paravirtualization features.
  • C. supportsIntelVT-x
    Indicates that one entity provides compatibility with or the capability to use Intel VT-x virtualization technology for another entity.
  • D. virtualizationType
    Indicates the specific method or technology by which a resource, system, or environment is virtualized.
  • E. supportsKVM
    Indicates that one entity provides compatibility with or the capability to run KVM (Kernel-based Virtual Machine) for another entity.
  • F. None of above. chosen

Provenance (4 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_69f01d816d7c8190a1fe27e3434041dc completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_6a0144c75aec81908bdd9e88f2af737a completed May 11, 2026, 2:53 a.m.
PD Predicate disambiguation batch_6a014405a2d48190a1d58b0b907ad696 completed May 11, 2026, 2:50 a.m.
PDg Predicate description generation batch_6a0144c6bd20819093562eb03dc5b2c8 completed May 11, 2026, 2:53 a.m.
Created at: April 28, 2026, 4:30 a.m.