Triple
T27750292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MS10-021 |
E702096
|
entity |
| Predicate | patches |
P26055
|
FINISHED |
| Object | Windows Help and Support Center vulnerabilities |
—
|
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: Windows Help and Support Center vulnerabilities | Statement: [MS10-021, patches, Windows Help and Support Center vulnerabilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patches Context triple: [MS10-021, patches, Windows Help and Support Center vulnerabilities]
-
A.
patchName
Indicates the specific name or identifier assigned to a software patch applied to an entity.
-
B.
panels
Indicates that one entity is composed of, covered by, or divided into flat sections or segments formed by another entity.
-
C.
lays
Indicates that one entity deposits or places something, typically eggs or objects, onto a surface or in a location.
-
D.
releases
chosen
Indicates that one entity causes something to be set free, emitted, or made available from its control or containment.
-
E.
points
Indicates that one entity directs attention, focus, or a physical/abstract indication toward another entity or location.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6371e33808190bd66d358dbd8d725 |
completed | May 2, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:19 p.m.