Triple
T8285781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | oVirt |
E193782
|
entity |
| Predicate | supportsOVFImportExport |
P60286
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [oVirt, supportsOVFImportExport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOVFImportExport Context triple: [oVirt, supportsOVFImportExport, yes]
-
A.
supportsImportExport
chosen
Indicates that one entity provides functionality for importing and exporting data or resources to and from another entity.
-
B.
supportsNestedVirtualization
Indicates that one computing environment or platform enables and correctly handles running virtual machines inside other virtual machines.
-
C.
virtualizationType
Indicates the specific method or technology by which a resource, system, or environment is virtualized.
-
D.
supportsCloudImages
Indicates that an entity is capable of handling, displaying, or otherwise working with images stored or managed in a cloud environment.
-
E.
supportsIntelVT-d
Indicates that one entity provides compatibility with or enables the use of Intel VT-d (Intel Virtualization Technology for Directed I/O) for another entity.
- 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_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. |
Created at: March 30, 2026, 5:52 p.m.