Triple
T8287039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Registry |
E193808
|
entity |
| Predicate | misconfigurationRisk |
P82535
|
FINISHED |
| Object | system malfunction |
—
|
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: system malfunction | Statement: [Windows Registry, misconfigurationRisk, system malfunction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: misconfigurationRisk Context triple: [Windows Registry, misconfigurationRisk, system malfunction]
-
A.
vulnerabilityType
Indicates the specific kind or category of vulnerability associated with an entity or situation.
-
B.
securityAdvisory
Indicates a relationship where an entity issues, references, or is associated with a warning or guidance about security vulnerabilities, risks, or protective measures.
-
C.
majorSecurityIssue
Indicates that the subject faces or causes a significant security vulnerability or threat.
-
D.
configuration
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
-
E.
securityRecommendation
Indicates that one entity advises or prescribes specific security-related actions, settings, or measures 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad4b2008190ad1624e1335147c6 |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:52 p.m.