Triple
T28611880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proxmox Backup Server |
E724184
|
entity |
| Predicate | supportsBackupType |
P203279
|
FINISHED |
| Object | virtual machines |
—
|
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: virtual machines | Statement: [Proxmox Backup Server, supportsBackupType, virtual machines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBackupType Context triple: [Proxmox Backup Server, supportsBackupType, virtual machines]
-
A.
supportsBackupCopy
Indicates that one entity provides the capability or functionality to create, maintain, or use a backup copy of another entity.
-
B.
supportsBackupTool
Indicates that one entity provides compatibility with or functionality for a specified backup tool.
-
C.
supportsBackupFormat
Indicates that one entity is capable of handling, storing, or operating with another entity as a backup data format.
-
D.
supportsBackupPolicies
Indicates that one entity provides or enforces backup policy capabilities or configurations for another entity.
-
E.
supportsBackupPlans
Indicates that an entity provides assistance, resources, or endorsement for alternative or contingency plans associated with another entity or situation.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a0149447e448190b0480943de0691ee |
completed | May 11, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_6a0148e2c39c8190a3ad6ea6be902c04 |
completed | May 11, 2026, 3:11 a.m. |
| PDg | Predicate description generation | batch_6a014943b7d481909fa2c1c3f176db24 |
completed | May 11, 2026, 3:13 a.m. |
Created at: April 28, 2026, 4:30 a.m.