Triple
T8285789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | oVirt |
E193782
|
entity |
| Predicate | supportsSPICEConsole |
P33108
|
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, supportsSPICEConsole, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSPICEConsole Context triple: [oVirt, supportsSPICEConsole, yes]
-
A.
supportsRemoteTerminal
Indicates that one entity provides or enables access to another entity via a remote terminal interface.
-
B.
supportsIntelVT-x
Indicates that one entity provides compatibility with or the capability to use Intel VT-x virtualization technology for another entity.
-
C.
virtualConsoleService
chosen
Indicates a relationship where a service provides or manages access to a virtual console interface for another entity.
-
D.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of 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_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.