Triple
T4980177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reaver (WPS attack tool) |
E111863
|
entity |
| Predicate | attackVector |
P4333
|
FINISHED |
| Object | WPS PIN |
—
|
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: WPS PIN | Statement: [Reaver (WPS attack tool), attackVector, WPS PIN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackVector Context triple: [Reaver (WPS attack tool), attackVector, WPS PIN]
-
A.
attackType
chosen
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
B.
attackProfile
Indicates a relationship where one entity initiates or carries out an aggressive or hostile action against another entity.
-
C.
attackToolExample
Indicates that a specific tool or method is used as an example of how an attack is or can be carried out.
-
D.
vulnerabilityType
Indicates the specific kind or category of vulnerability associated with an entity or situation.
-
E.
attackOccurred
Indicates that an act of aggression or violence was carried out by one party against another.
- 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_69bd441adc208190b70a033a0741d01e |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd7146e6e881908a55ab2756b631f6 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.