Triple
T36312840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anonymous (collective) |
E894107
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hacktivist collective |
C7451
|
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: hacktivist collective Context triple: [Anonymous (collective), instanceOf, hacktivist collective]
-
A.
clandestine group
chosen
A clandestine group is a secretive organization whose members covertly coordinate activities, often to pursue hidden political, criminal, or subversive objectives while avoiding detection by authorities or the public.
-
B.
expellee organization
An expellee organization is a group formed to represent, support, and advocate for the rights, interests, and cultural heritage of people who have been forcibly displaced or expelled from their homes or homelands.
-
C.
program of the Electronic Frontier Foundation
A program of the Electronic Frontier Foundation is an organized initiative or project designed to protect and promote digital civil liberties, such as privacy, free expression, and innovation, through advocacy, education, and legal action.
-
D.
hoax organization
A hoax organization is a fictitious or misleading entity presented as a legitimate group or institution, typically created to deceive, satirize, or manipulate public perception.
-
E.
cypherpunk
A cypherpunk is an individual who advocates for and actively uses strong cryptography and privacy-enhancing technologies as tools for social and political change, particularly to protect individual freedom from surveillance and centralized control.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.