Triple
T8285875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proxmox VE |
E193783
|
entity |
| Predicate | supportsBackupFormat |
P82525
|
FINISHED |
| Object | QEMU backup format |
—
|
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 backup format | Statement: [Proxmox VE, supportsBackupFormat, QEMU backup format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBackupFormat Context triple: [Proxmox VE, supportsBackupFormat, QEMU backup format]
-
A.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
B.
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.
-
C.
servesAsBackupFor
Indicates that one entity functions as a substitute or fallback that can take over the role or responsibilities of another entity if needed.
-
D.
hasWorkingFormat
Indicates that one entity possesses or is associated with a functional or operational format of another entity.
-
E.
canImportFormat
Indicates that an entity has the capability to import or read data in a specified format.
- 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_69cb7ad3722481908076508908d18621 |
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.