Triple
T14396099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAST |
E356952
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Security testing methodology |
C30890
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Security testing methodology Context triple: [SAST, instanceOf, Security testing methodology]
-
A.
security practice
chosen
A security practice is a repeatable method, process, or behavior designed to protect systems, data, and users from threats and vulnerabilities.
-
B.
security auditing tool
A security auditing tool is a software application that systematically scans, analyzes, and reports on systems, networks, or applications to identify security vulnerabilities, misconfigurations, and compliance issues.
-
C.
software development methodology
A software development methodology is a structured framework of principles, practices, and processes that guides how software is planned, designed, built, tested, and delivered.
-
D.
software testing program
A software testing program is an application designed to automatically execute tests on other software to verify functionality, detect defects, and ensure quality against specified requirements.
-
E.
Application security vendor
An application security vendor provides tools and services that identify, prevent, and remediate security vulnerabilities in software applications throughout their development and deployment lifecycle.
- F. None of above.
Provenance (1 batch)
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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:17 a.m.