Triple
T32536277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OWASP |
E831598
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | software security organization |
C20451
|
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: software security organization Context triple: [OWASP, instanceOf, software security organization]
-
A.
software security technology
Software security technology encompasses the tools, techniques, and practices designed to protect software systems from vulnerabilities, attacks, and unauthorized access throughout their lifecycle.
-
B.
security software initiative
A security software initiative is a coordinated effort to design, develop, and deploy tools and processes that protect digital systems, data, and users from threats and vulnerabilities.
-
C.
security program
A security program is an organized set of policies, processes, technologies, and resources designed to protect an organization’s assets, information, and operations from threats and vulnerabilities.
-
D.
software engineering organization
chosen
A software engineering organization is a structured group of people, processes, and tools dedicated to designing, building, testing, deploying, and maintaining software systems to meet specific business or user needs.
-
E.
security architecture
Security architecture is the structured design of an organization's security controls, principles, and technologies that work together to protect systems, data, and operations from threats and vulnerabilities.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:01 a.m.