Triple
T5919903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coders’ Rights Project |
E131674
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | security research advocacy program |
C19560
|
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 research advocacy program Context triple: [Coders’ Rights Project, instanceOf, security research advocacy program]
-
A.
privacy engineering program
A privacy engineering program is an organized, cross-functional initiative that systematically embeds privacy requirements, risk management, and privacy-by-design practices into an organization’s products, services, and technical infrastructure.
-
B.
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.
-
C.
security advocate
A security advocate is a professional who champions, educates, and influences best practices in security across teams and organizations to reduce risk and promote a strong security culture.
-
D.
research center program
A research center program is an organized initiative within a research institution that coordinates projects, resources, and collaborations to advance inquiry and innovation in a specific field or set of related disciplines.
-
E.
cooperative security activity
A cooperative security activity is a coordinated effort among multiple actors—such as states, organizations, or agencies—to jointly prevent, mitigate, or respond to security threats through shared information, resources, and actions.
- 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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4 p.m.