Triple
T14087161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QCOW (via conversion) |
E339026
|
entity |
| Predicate | conversionTool |
P105178
|
FINISHED |
| Object | qemu-img |
—
|
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: qemu-img | Statement: [QCOW (via conversion), conversionTool, qemu-img]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionTool Context triple: [QCOW (via conversion), conversionTool, qemu-img]
-
A.
conversionUse
Indicates that one entity is used as a means, method, or context for converting another entity from one form, state, or representation to another.
-
B.
conversionProgram
chosen
Indicates a program or process that transforms something from one form, state, or type into another.
-
C.
conversionTarget
Indicates that one entity serves as the intended outcome, goal, or result that another entity is meant to be converted or transformed into.
-
D.
convertedUnit
Indicates that one unit is the result of converting a quantity expressed in another unit.
-
E.
conversionProcess
Indicates a process in which something is transformed or changed from one state, form, or representation into another.
- F. None of above.
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. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.