Triple
T28617579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Virtual Server |
E724306
|
entity |
| Predicate | supportsSnapshot |
P203
|
FINISHED |
| Object | virtual machine snapshots |
—
|
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 machine snapshots | Statement: [Microsoft Virtual Server, supportsSnapshot, virtual machine snapshots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSnapshot Context triple: [Microsoft Virtual Server, supportsSnapshot, virtual machine snapshots]
-
A.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
B.
supportsImage
Indicates that one entity is capable of handling, displaying, or processing image data associated with another entity.
-
C.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
D.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
E.
supportsSince
Indicates that one entity has been providing support to another entity starting from a specific point in time and continuing thereafter.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a017969ff908190a7a1a46b3f5ae362 |
completed | May 11, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a017609ff4c8190aba8a1864d39a608 |
completed | May 11, 2026, 6:24 a.m. |
Created at: April 28, 2026, 4:32 a.m.