Triple
T28508321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meterpreter |
E721417
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | penetration testing payload |
C23790
|
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: penetration testing payload Context triple: [Meterpreter, instanceOf, penetration testing payload]
-
A.
social engineering toolkit
A social engineering toolkit is a collection of tools and frameworks designed to simulate, execute, and analyze social engineering attacks such as phishing, pretexting, and credential harvesting for security testing and training purposes.
-
B.
red team tool
A red team tool is a software or framework used by security professionals to simulate real-world attacks on systems and networks in order to identify vulnerabilities and improve defensive measures.
-
C.
browser exploitation framework
A browser exploitation framework is a specialized software platform that automates the discovery, development, and execution of exploits targeting web browsers and their components to assess or compromise client-side security.
-
D.
post-exploitation framework
chosen
A post-exploitation framework is a toolkit used after initial system compromise to maintain access, escalate privileges, move laterally, and exfiltrate data within a target environment.
-
E.
Metasploit GUI front-end
A Metasploit GUI front-end is a graphical user interface application that simplifies interaction with the Metasploit Framework by providing visual tools for configuring exploits, managing targets, and viewing results.
- 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:10 a.m.