Triple
T22498731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EFF Technology Projects |
E556212
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | privacy technology initiative |
C12160
|
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: privacy technology initiative Context triple: [EFF Technology Projects, instanceOf, privacy technology initiative]
-
A.
privacy engineering program
chosen
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.
privacy protection software
Privacy protection software is a class of applications designed to safeguard users' personal data and online activities by controlling access, encrypting information, and preventing unauthorized tracking or disclosure.
-
C.
privacy law
Privacy law is the body of legal rules and principles that governs the collection, use, storage, and disclosure of personal information to protect individuals’ privacy rights.
-
D.
security initiative
A security initiative is a coordinated set of actions, policies, and resources designed to improve an organization’s protection against threats and vulnerabilities.
-
E.
security research advocacy program
A security research advocacy program is an organized initiative that promotes, supports, and coordinates ethical security research and responsible vulnerability disclosure between researchers, organizations, and the broader community.
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.