Triple
T14087172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QCOW (via conversion) |
E339026
|
entity |
| Predicate | supportsBackingFiles |
P112768
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [QCOW (via conversion), supportsBackingFiles, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBackingFiles Context triple: [QCOW (via conversion), supportsBackingFiles, true]
-
A.
supportsBackupFormat
Indicates that one entity is capable of handling, storing, or operating with another entity as a backup data format.
-
B.
supportsAttachments
Indicates that the subject is capable of handling or allowing the inclusion of file or data attachments in its operation or context.
-
C.
supportsBackupTool
Indicates that one entity provides compatibility with or functionality for a specified backup tool.
-
D.
supportsBackupCopy
Indicates that one entity provides the capability or functionality to create, maintain, or use a backup copy of another entity.
-
E.
supportsMultipleFiles
Indicates that the subject is capable of handling, processing, or operating on more than one file at the same time.
- 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_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. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:21 p.m.