Triple
T28509964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raphael Mudge |
E721453
|
entity |
| Predicate | toolArmitageType |
P86841
|
FINISHED |
| Object | graphical cyber attack management tool for Metasploit |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: graphical cyber attack management tool for Metasploit | Statement: [Raphael Mudge, toolArmitageType, graphical cyber attack management tool for Metasploit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toolArmitageType Context triple: [Raphael Mudge, toolArmitageType, graphical cyber attack management tool for Metasploit]
-
A.
toolType
chosen
Indicates the specific kind or category of tool associated with an entity.
-
B.
attackToolExample
Indicates that a specific tool or method is used as an example of how an attack is or can be carried out.
-
C.
toolIn
Indicates that one entity is a tool or instrument used in or associated with another entity or context.
-
D.
usesToolType
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
-
E.
toolkitName
Indicates that an entity is associated with or identified by the name of a specific toolkit.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69f64f750780819096870b32a7f4b35f |
completed | May 2, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:11 a.m.