Triple
T8285601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QEMU |
E193779
|
entity |
| Predicate | supportsDiskImageFormat |
P82508
|
FINISHED |
| Object | qcow |
—
|
LITERAL 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: qcow | Statement: [QEMU, supportsDiskImageFormat, qcow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDiskImageFormat Context triple: [QEMU, supportsDiskImageFormat, qcow]
-
A.
supportsInstallationMedia
Indicates that one entity is capable of accepting, handling, or working with a specified type of installation media for setup or deployment purposes.
-
B.
supportsPhysicalMedia
Indicates that one entity provides the capability to use, read, or handle physical media formats (such as discs, tapes, or printed materials) associated with another entity.
-
C.
hasFileFormat
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
D.
supportsPartitionTable
Indicates that one entity provides the capability to create, manage, or operate on partitioned tables for another entity.
-
E.
supportsCloudImages
Indicates that an entity is capable of handling, displaying, or otherwise working with images stored or managed in a cloud environment.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad20ae481908179aba245c73fad |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:52 p.m.