Triple
T32550430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACM SIGSAC Outstanding Innovation Award |
E831958
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | computer security award |
C61731
|
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: computer security award Context triple: [ACM SIGSAC Outstanding Innovation Award, instanceOf, computer security award]
-
A.
cryptography award
A cryptography award is a formal recognition given to individuals or groups for significant contributions, innovations, or achievements in the field of cryptography and information security.
-
B.
information systems award
An information systems award is a formal recognition given to individuals, teams, or organizations for outstanding achievements, innovation, or contributions in the design, implementation, or management of information systems.
-
C.
software development award
A software development award is a formal recognition given to individuals, teams, or organizations for outstanding achievements, innovation, or excellence in creating, maintaining, or improving software products and development practices.
-
D.
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.
-
E.
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.
- F. None of above. chosen
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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:02 a.m.