Triple
T8724285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linux kernel |
E207089
|
entity |
| Predicate | supportsKVM |
P84281
|
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: [Linux kernel, supportsKVM, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsKVM Context triple: [Linux kernel, supportsKVM, true]
-
A.
supportsParavirtualization
Indicates that one entity provides the capability for another entity to run in a paravirtualized environment or to use paravirtualization features.
-
B.
KVMUses
Indicates that a KVM (Kernel-based Virtual Machine) relies on, employs, or makes use of another component, resource, or technology to function or provide its virtualization capabilities.
-
C.
supportsNestedVirtualization
Indicates that one computing environment or platform enables and correctly handles running virtual machines inside other virtual machines.
-
D.
supportsIntelVT-x
Indicates that one entity provides compatibility with or the capability to use Intel VT-x virtualization technology for another entity.
-
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. 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d1404948190bc45d14a1ddb1a7e |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc489dd528819084ed5d88bd8bb3d6 |
completed | March 31, 2026, 10:20 p.m. |
Created at: March 30, 2026, 6:36 p.m.