Triple
T11656389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQL Server Authentication |
E277020
|
entity |
| Predicate | securityRisk |
P91654
|
FINISHED |
| Object | password exposure over network if not encrypted |
—
|
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: password exposure over network if not encrypted | Statement: [SQL Server Authentication, securityRisk, password exposure over network if not encrypted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityRisk Context triple: [SQL Server Authentication, securityRisk, password exposure over network if not encrypted]
-
A.
securityImplication
chosen
Indicates that one entity has a consequence, effect, or relevance for the safety, protection, or vulnerability status of another entity or system.
-
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.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
D.
security
Indicates that an entity provides protection, safety measures, or safeguards to another entity or against specific threats or risks.
-
E.
riskAddressed
Indicates that a particular risk has been identified and is being mitigated, managed, or otherwise handled by an associated action, control, or measure.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d0331481909682b2e504e4c9a0 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.