Triple
T8249016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Responder |
E192910
|
entity |
| Predicate | implementsAttack |
P4333
|
FINISHED |
| Object | LLMNR poisoning |
—
|
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: LLMNR poisoning | Statement: [Responder, implementsAttack, LLMNR poisoning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementsAttack Context triple: [Responder, implementsAttack, LLMNR poisoning]
-
A.
attackType
chosen
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
B.
attackedFrom
Indicates that one entity initiated an attack against another entity originating from a specific source location or position.
-
C.
numberOfAttacks
Indicates the count of distinct attack events associated with a given entity or interaction.
-
D.
attacksIf
Indicates that one entity initiates or carries out an attack on another entity when certain conditions are met.
-
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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78c6b3c48190a3ecebf449766124 |
completed | March 31, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.