Triple
T14087147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QCOW (via conversion) |
E339026
|
entity |
| Predicate | usedBy |
P260
|
FINISHED |
| Object | QEMU |
E193779
|
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: QEMU | Statement: [QCOW (via conversion), usedBy, QEMU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: QEMU Context triple: [QCOW (via conversion), usedBy, QEMU]
-
A.
QEMU
chosen
QEMU is an open-source machine emulator and virtualizer that enables running operating systems and programs for one hardware platform on another.
-
B.
VirtualBox
VirtualBox is a popular open-source virtualization platform that allows users to run multiple operating systems simultaneously on a single physical machine.
-
C.
PowerKVM
PowerKVM is IBM’s KVM-based virtualization solution tailored for IBM Power Systems servers, enabling Linux-based virtual machine management and consolidation.
-
D.
QMP (QEMU Machine Protocol)
QMP (QEMU Machine Protocol) is a JSON-based control protocol that allows external programs to monitor and manage QEMU virtual machines programmatically.
-
E.
VMware Workstation
VMware Workstation is a desktop virtualization software application 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5ee1ce88819091c983286289337e |
completed | April 14, 2026, 3:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcdefe88b481908b3dca1f019e7809 |
completed | May 7, 2026, 6:50 p.m. |
Created at: April 9, 2026, 10:21 p.m.