Triple
T28508752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hacker’s Choice |
E721426
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hacking collective |
C15257
|
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: hacking collective Context triple: [The Hacker’s Choice, instanceOf, hacking collective]
-
A.
Internet Security Research Group
The Internet Security Research Group is a nonprofit organization dedicated to improving internet security by promoting and providing accessible, open, and automated security technologies and practices.
-
B.
collective
chosen
A collective is a group of individuals who voluntarily unite to pursue shared goals, interests, or actions, often emphasizing collaboration and shared decision-making over hierarchical structures.
-
C.
open-source intelligence collective
An open-source intelligence collective is a collaborative group that gathers, analyzes, and shares publicly available information to produce actionable insights for research, security, or advocacy purposes.
-
D.
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.
-
E.
clandestine group
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.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:11 a.m.