task
stringclasses 7
values | dataset
stringclasses 34
values | subset
stringclasses 1
value | instruction
stringclasses 7
values | content
stringlengths 1
8.18k
| output
stringlengths 4
3.74k
| schema
stringclasses 79
values | negative_labels
stringclasses 55
values | json
stringlengths 14
6.84k
| system_prompt
stringclasses 7
values |
|---|---|---|---|---|---|---|---|---|---|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The attackers favour using URL shortening services to disguise the true links they are sending in spear phishing emails .
|
phishing: are sending | attacker: they | tool: spear phishing emails
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "are sending", "arguments": [{"name": "spear phishing emails", "role": "tool"}, {"name": "they", "role": "attacker"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The initial phishes came in from a K12 domain from several affected individuals .
|
phishing: came in | trusted entity: a K12 domain | trusted entity: individuals
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "came in", "arguments": [{"name": "a K12 domain", "role": "trusted entity"}, {"name": "individuals", "role": "trusted entity"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
More likely than not , they have simply written a script that takes specific info from the Ashley Madison data dump , inserts it in a template email , and fires these emails off to as many recipients as possible .
|
data breach: data dump | victim: Ashley Madison
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "data dump", "arguments": [{"name": "Ashley Madison", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
These particular set of attacks show a deep knowledge of social engineering , and especially phishing tactics .
|
phishing: attacks | attack pattern: especially phishing tactics
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "attacks", "arguments": [{"name": "especially phishing tactics", "role": "attack pattern"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
A few months ago we exclusively reported on a Dark Web vendor selling 1 Billion user accounts stolen from the Chinese Internet giants .
|
data breach: stolen | attacker: a Dark Web vendor | compromised data: user accounts | number of data: 1 Billion | purpose: selling | time: A few months ago | victim: the Chinese Internet giants
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "stolen", "arguments": [{"name": "selling", "role": "purpose"}, {"name": "user accounts", "role": "compromised data"}, {"name": "the Chinese Internet giants", "role": "victim"}, {"name": "a Dark Web vendor", "role": "attacker"}, {"name": "A few months ago", "role": "time"}, {"name": "1 Billion", "role": "number of data"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The following year , PhineasFisher targeted Italian company Hacking Team , and published a trove of emails and other internal documents from the company .
|
data breach: published | attacker: PhineasFisher | compromised data: a trove of emails | compromised data: internal documents | victim: Italian company Hacking Team | victim: the company
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "published", "arguments": [{"name": "Italian company Hacking Team", "role": "victim"}, {"name": "PhineasFisher", "role": "attacker"}, {"name": "a trove of emails", "role": "compromised data"}, {"name": "internal documents", "role": "compromised data"}, {"name": "the company", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
" We are investigating alleged unauthorized access to our online portal where a person or persons using stolen credentials accessed W - 2 information of a limited number of individuals , " an Equifax spokesperson told El Reg on Monday .
|
data breach: unauthorized access | victim: our online portal
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "unauthorized access", "arguments": [{"name": "our online portal", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The fake site was previously used in a spear phishing email attack to spread Windows malware and is believed to be maintained by Iranian hackers , the researchers claimed .
|
phishing: a spear phishing email attack | attacker: Iranian hackers | purpose: spread Windows malware | tool: The fake site
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "a spear phishing email attack", "arguments": [{"name": "spread Windows malware", "role": "purpose"}, {"name": "Iranian hackers", "role": "attacker"}, {"name": "The fake site", "role": "tool"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
You may have heard of the CEO scam : that ’s where spear - phishers impersonate a CEO to hit up a company for sensitive information .
|
phishing: impersonate | attacker: spear - phishers | purpose: sensitive information | trusted entity: a CEO
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "impersonate", "arguments": [{"name": "spear - phishers", "role": "attacker"}, {"name": "sensitive information", "role": "purpose"}, {"name": "a CEO", "role": "trusted entity"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The vulnerability , disclosed on Monday , affects features in Intel firmware that are designed for enterprise IT management .
|
discover vulnerability: disclosed | time: Monday | vulnerability: The vulnerability
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "disclosed", "arguments": [{"name": "The vulnerability", "role": "vulnerability"}, {"name": "Monday", "role": "time"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
One of the largest hacks ever was disclosed this month , when credit reporting company Equifax Inc. revealed that sensitive data from 143 million consumers , including Social Security numbers and birth dates , was exposed .
|
data breach: was exposed | compromised data: Social Security numbers | compromised data: birth dates | compromised data: sensitive data | number of victim: 143 million | victim: consumers
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "was exposed", "arguments": [{"name": "birth dates", "role": "compromised data"}, {"name": "Social Security numbers", "role": "compromised data"}, {"name": "sensitive data", "role": "compromised data"}, {"name": "143 million", "role": "number of victim"}, {"name": "consumers", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
IRS screen captures show that the fake login pages created by the crooks look just like those on the real IRS site .
|
phishing: created | attacker: the crooks | tool: the fake login pages
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "created", "arguments": [{"name": "the crooks", "role": "attacker"}, {"name": "the fake login pages", "role": "tool"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Malware posing as legitimate software for Siemens control gear has apparently infected industrial equipment worldwide over the past four years .
|
phishing: posing as | purpose: infected industrial equipment worldwide | time: over the past four years | tool: Malware | trusted entity: Siemens | trusted entity: legitimate software
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "posing as", "arguments": [{"name": "legitimate software", "role": "trusted entity"}, {"name": "Malware", "role": "tool"}, {"name": "infected industrial equipment worldwide", "role": "purpose"}, {"name": "over the past four years", "role": "time"}, {"name": "Siemens", "role": "trusted entity"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Taking into account the copycat nature of the malware scene , this new trick of collecting driver 's license information will most likely spread to other PoS malware families .
|
data breach: collecting | compromised data: driver #$%#s license information | tool: PoS malware families
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "collecting", "arguments": [{"name": "driver #$%#s license information", "role": "compromised data"}, {"name": "PoS malware families", "role": "tool"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The computer hack cost the county more than $ 50,000 , Bubb said , which includes insurance and overtime , but he does not regret refusing to pay the demand .
|
ransom: pay the demand | attack pattern: The computer hack | damage amount: 50,000 | victim: he
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "pay the demand", "arguments": [{"name": "he", "role": "victim"}, {"name": "The computer hack", "role": "attack pattern"}, {"name": "50,000", "role": "damage amount"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Hacker seems to be interested in databases that contain important information / data or he chooses companies that are most likely in a position to pay the ransom to get their data back .
|
ransom: pay the ransom | attacker: Hacker | attacker: he | victim: companies
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "pay the ransom", "arguments": [{"name": "companies", "role": "victim"}, {"name": "he", "role": "attacker"}, {"name": "Hacker", "role": "attacker"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Instead , most keep attacks a secret , paying off hackers 70 percent of the time .
|
ransom: paying off | attacker: hackers
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "paying off", "arguments": [{"name": "hackers", "role": "attacker"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The FBI warning cites research conducted by the University of Michigan in 2015 that revealed more than 1 million FTP servers allowed anonymous access to stored data The FBI warns that hackers are targeting these anonymous FTP servers to gain access to the protected health information of patients .
|
discover vulnerability: warning | discoverer: The FBI
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "warning", "arguments": [{"name": "The FBI", "role": "discoverer"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
“ There is no indication that any financial , password or other sensitive personal information was accessed , ” the company noted , and added that the incident is not connected to the recent global WannaCry malware attacks .
|
data breach: was accessed | compromised data: password | compromised data: sensitive personal information
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "was accessed", "arguments": [{"name": "sensitive personal information", "role": "compromised data"}, {"name": "password", "role": "compromised data"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
All three groups say that the issues have yet to be fixed by Western Digital .
|
patch vulnerability: be fixed | releaser: Western Digital | vulnerability: the issues
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "patch vulnerability", "trigger": "be fixed", "arguments": [{"name": "Western Digital", "role": "releaser"}, {"name": "the issues", "role": "vulnerability"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The organization did not pay .
|
ransom: pay | victim: The organization
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "pay", "arguments": [{"name": "The organization", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
" There is this stream of liability that flows from the ransomware attack , " he said " That 's liability to individuals , consumers and patients , " WannaCry exploits a vulnerability in older versions of Windows , including Windows 7 and Windows XP .
|
discover vulnerability: exploits | vulnerability: a vulnerability | vulnerable system version: older versions | vulnerable system: Windows | vulnerable system: Windows 7 | vulnerable system: Windows XP
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "exploits", "arguments": [{"name": "a vulnerability", "role": "vulnerability"}, {"name": "older versions", "role": "vulnerable system version"}, {"name": "Windows", "role": "vulnerable system"}, {"name": "Windows 7", "role": "vulnerable system"}, {"name": "Windows XP", "role": "vulnerable system"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
That breach , which only became public last year , involved the theft of user account details such as email addresses , telephone numbers , and hashed passwords .
|
data breach: That breach | time: last year
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "That breach", "arguments": [{"name": "last year", "role": "time"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
" Unfortunately , you are hacked , " the start of the malware 's ransom demand reportedly reads .
|
ransom: the malware #$%#s ransom demand
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "the malware #$%#s ransom demand", "arguments": []}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
On Thursday , the Shadow Brokers dumped them online after an attempt to sell these and other supposedly Windows and Unix hacking tools for bitcoin .
|
data breach: dumped | attacker: the Shadow Brokers | compromised data: Windows and Unix hacking tools | compromised data: them | purpose: an attempt to sell these | time: Thursday
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "dumped", "arguments": [{"name": "them", "role": "compromised data"}, {"name": "the Shadow Brokers", "role": "attacker"}, {"name": "Thursday", "role": "time"}, {"name": "an attempt to sell these", "role": "purpose"}, {"name": "Windows and Unix hacking tools", "role": "compromised data"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The zero - day memory corruption flaw resides in the implementation of the SMB ( server message block ) network file sharing protocol that could allow a remote , unauthenticated attacker to crash systems with denial of service attack , which would then open them to more possible attacks .
|
discover vulnerability: resides in | capabilities: crash systems with denial of service attack | vulnerability: zero - day memory corruption flaw | vulnerable system: SMB ( server message block
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "resides in", "arguments": [{"name": "zero - day memory corruption flaw", "role": "vulnerability"}, {"name": "SMB ( server message block", "role": "vulnerable system"}, {"name": "crash systems with denial of service attack", "role": "capabilities"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The Shadow Brokers first emerged on social media in August by similarly dumping operational code for a cohort of old firewall exploits that targeted vulnerabilities in Cisco , Fortinet and Juniper Networks products .
|
discover vulnerability: first emerged | discoverer: The Shadow Brokers | vulnerability: a cohort of old firewall exploits | vulnerability: vulnerabilities | vulnerable system owner: Cisco | vulnerable system owner: Fortinet | vulnerable system owner: Juniper | vulnerable system: Networks products
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "first emerged", "arguments": [{"name": "vulnerabilities", "role": "vulnerability"}, {"name": "The Shadow Brokers", "role": "discoverer"}, {"name": "Networks products", "role": "vulnerable system"}, {"name": "a cohort of old firewall exploits", "role": "vulnerability"}, {"name": "Cisco", "role": "vulnerable system owner"}, {"name": "Fortinet", "role": "vulnerable system owner"}, {"name": "Juniper", "role": "vulnerable system owner"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Ultimately , if stitched together , he warns , the bugs could result in session hijacking , persistent phishing attacks , and persistent redirect to external sources .
|
discover vulnerability: warns | capabilities: persistent phishing attacks | capabilities: persistent redirect to external sources | capabilities: result in session hijacking | discoverer: he | vulnerability: the bugs
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "warns", "arguments": [{"name": "he", "role": "discoverer"}, {"name": "the bugs", "role": "vulnerability"}, {"name": "result in session hijacking", "role": "capabilities"}, {"name": "persistent phishing attacks", "role": "capabilities"}, {"name": "persistent redirect to external sources", "role": "capabilities"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
It 's pretty much always a good idea to keep your computer 's operating system fully up to date , especially when news of critical security issues comes to light .
|
patch vulnerability: fully up to date | vulnerability: critical security issues | vulnerable system: computer | vulnerable system: operating system
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "patch vulnerability", "trigger": "fully up to date", "arguments": [{"name": "critical security issues", "role": "vulnerability"}, {"name": "operating system", "role": "vulnerable system"}, {"name": "computer", "role": "vulnerable system"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Attackers may try to get onto these networks and lay dormant … then steal intellectual property or cause other damage .
|
data breach: steal | attacker: Attackers | compromised data: intellectual property | victim: networks
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "steal", "arguments": [{"name": "networks", "role": "victim"}, {"name": "intellectual property", "role": "compromised data"}, {"name": "Attackers", "role": "attacker"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
But as of lunchtime the attackers had claimed only about $ 92,000 ( € 82,183 ) in payments from their widespread ransom demands , according to Elliptic Enterprises Ltd , a UK - based company that tracks illicit use of bitcoin .
|
ransom: ransom demands | attacker: the attackers | price: 92,000 | price: € 82,183
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "ransom demands", "arguments": [{"name": "the attackers", "role": "attacker"}, {"name": "92,000", "role": "price"}, {"name": "€ 82,183", "role": "price"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
" After few trials and errors trying to reproduce the issue , I found that the very first call to passwordrecovered.cgi will give out the credentials no matter what the parameter you send .
|
discover vulnerability: found | capabilities: passwordrecovered.cgi will give out the credentials | discoverer: I | vulnerability: the issue
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "found", "arguments": [{"name": "I", "role": "discoverer"}, {"name": "the issue", "role": "vulnerability"}, {"name": "passwordrecovered.cgi will give out the credentials", "role": "capabilities"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
At the end of April , the same hacker group leaked the first ten episodes of season 5 of Netflix 's " Orange Is The New Black " series .
|
data breach: leaked | attacker: hacker group | compromised data: first ten episodes | time: end of April | victim: Netflix
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "leaked", "arguments": [{"name": "Netflix", "role": "victim"}, {"name": "hacker group", "role": "attacker"}, {"name": "end of April", "role": "time"}, {"name": "first ten episodes", "role": "compromised data"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The following year , PhineasFisher targeted Italian company Hacking Team , and published a trove of emails and other internal documents from the company .
|
data breach: published | attacker: PhineasFisher | compromised data: a trove of emails | compromised data: internal documents | victim: Italian company Hacking Team | victim: the company
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "published", "arguments": [{"name": "Italian company Hacking Team", "role": "victim"}, {"name": "PhineasFisher", "role": "attacker"}, {"name": "a trove of emails", "role": "compromised data"}, {"name": "internal documents", "role": "compromised data"}, {"name": "the company", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
After the ransacking of MongoDB , ElasticSearch , Hadoop , CouchDB , and Cassandra servers , attackers are now hijacking hundreds of MySQL databases , deleting their content , and leaving a ransom note behind asking for a 0.2 Bitcoin ( $ 235 ) payment .
|
data breach: the ransacking | victim: Cassandra servers | victim: CouchDB | victim: ElasticSearch | victim: Hadoop | victim: MongoDB
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "the ransacking", "arguments": [{"name": "MongoDB", "role": "victim"}, {"name": "ElasticSearch", "role": "victim"}, {"name": "Hadoop", "role": "victim"}, {"name": "CouchDB", "role": "victim"}, {"name": "Cassandra servers", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
This was possible due to a system vulnerability that the infiltrator exploited to access some data provided by some customers of ABTA Members and by ABTA Members themselves .
|
data breach: access | compromised data: data | victim: ABTA Members | victim: some customers of ABTA Members
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "access", "arguments": [{"name": "data", "role": "compromised data"}, {"name": "some customers of ABTA Members", "role": "victim"}, {"name": "ABTA Members", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
A massive phishing campaign took place today , but Google 's security staff was on hand and shut down the attacker 's efforts within an hour after users first reported the problem on Reddit .
|
phishing: A massive phishing campaign | time: today
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "A massive phishing campaign", "arguments": [{"name": "today", "role": "time"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The ransom amount itself was $ 500 although even paying that would have been difficult because there was no way to click on the payment section to find the instructions on how to do so .
|
ransom: paying | payment method: click on the payment section | price: 500
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "paying", "arguments": [{"name": "500", "role": "price"}, {"name": "click on the payment section", "role": "payment method"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The criminal then attempts to trick the target into giving away their personal or financial information , such as passwords , payment card details or bank account information .
|
phishing: trick | attacker: The criminal | purpose: giving away their personal or financial information | victim: the target
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "trick", "arguments": [{"name": "the target", "role": "victim"}, {"name": "The criminal", "role": "attacker"}, {"name": "giving away their personal or financial information", "role": "purpose"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
It ’s difficult to tell how many of these devices are still vulnerable but , as DefenseCode ’s Leon Juranic pointed out to me , users rarely ( if ever ) update their router ’s firmware , so there are bound to be still many of them .
|
discover vulnerability: are still vulnerable | vulnerable system: these devices
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "are still vulnerable", "arguments": [{"name": "these devices", "role": "vulnerable system"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The Guardian report cited research by Tobias Boelter , a cryptography and security researcher at the University of California , Berkeley .
|
discover vulnerability: report | discoverer: The Guardian
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "report", "arguments": [{"name": "The Guardian", "role": "discoverer"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The bug , which was first spotted by researchers at Check Point , is caused by a development oversight in Android permissions , which in the past required users to manually grant downloaded applications the ability to display content on top of other app panes .
|
discover vulnerability: spotted | capabilities: manually grant downloaded applications the ability | discoverer: Check Point | discoverer: researchers | vulnerability: The bug
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "spotted", "arguments": [{"name": "researchers", "role": "discoverer"}, {"name": "Check Point", "role": "discoverer"}, {"name": "The bug", "role": "vulnerability"}, {"name": "manually grant downloaded applications the ability", "role": "capabilities"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
In fact , our tests show that one of the models listed as not vulnerable ( DGN2200v4 ) is , in fact , vulnerable and this can easily be reproduced with the POC provided in our advisory .
|
discover vulnerability: listed as not vulnerable | vulnerable system version: DGN2200v4 | vulnerable system: models
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "listed as not vulnerable", "arguments": [{"name": "models", "role": "vulnerable system"}, {"name": "DGN2200v4", "role": "vulnerable system version"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
In a new twist , this year ’s spam scamwich also features a followup email from that “ executive ” , sent to payroll or the comptroller , asking for a wire transfer to a certain account .
|
phishing: sent to | purpose: asking for a wire transfer to a certain account | trusted entity: email | trusted entity: executive | victim: payroll | victim: the comptroller
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "sent to", "arguments": [{"name": "executive", "role": "trusted entity"}, {"name": "payroll", "role": "victim"}, {"name": "asking for a wire transfer to a certain account", "role": "purpose"}, {"name": "the comptroller", "role": "victim"}, {"name": "email", "role": "trusted entity"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
But according to The Register , workers still have n't been told about the breach , which took place in September .
|
data breach: the breach | time: September | victim: workers
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "the breach", "arguments": [{"name": "workers", "role": "victim"}, {"name": "September", "role": "time"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Before it was fixed , like this week ’s issue , an attacker could have remotely injected script into invoices , something that could have lead to hijacking , phishing , and redirect .
|
patch vulnerability: was fixed | issues addressed: attacker could have remotely injected script into invoices | issues addressed: lead to hijacking , phishing , and redirect | vulnerability: it | vulnerability: this week ’s issue
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "patch vulnerability", "trigger": "was fixed", "arguments": [{"name": "attacker could have remotely injected script into invoices", "role": "issues addressed"}, {"name": "lead to hijacking , phishing , and redirect", "role": "issues addressed"}, {"name": "it", "role": "vulnerability"}, {"name": "this week ’s issue", "role": "vulnerability"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
That ’s why over 70 % of the most common BEC subject line families appraised by Proofpoint featured the words “ Urgent ” , “ Payment ” and “ Request ” .
|
phishing: BEC
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "BEC", "arguments": []}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
This is how the researcher tracked down at least 30 other victims of Malik 's expert phishing attacks .
|
phishing: expert phishing attacks | attacker: Malik | victim: victims
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "expert phishing attacks", "arguments": [{"name": "victims", "role": "victim"}, {"name": "Malik", "role": "attacker"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Tavis Ormandy announced during the weekend that he and another Project Zero researcher Natalie Silvanovich discovered " the worst Windows remote code [ execution vulnerability ] in recent memory .
|
discover vulnerability: discovered | discoverer: Project Zero researcher Natalie Silvanovich | discoverer: Tavis Ormandy | discoverer: he | time: the weekend | vulnerability: execution vulnerability
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "discovered", "arguments": [{"name": "Project Zero researcher Natalie Silvanovich", "role": "discoverer"}, {"name": "Tavis Ormandy", "role": "discoverer"}, {"name": "he", "role": "discoverer"}, {"name": "the weekend", "role": "time"}, {"name": "execution vulnerability", "role": "vulnerability"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
According to The Guardian , the company became aware of a problem last week but only realized on Friday that data could be accessed externally , and only started contacting affected customers on Saturday .
|
data breach: could be accessed | compromised data: that data | time: Friday | time: Saturday | time: last week | victim: customers | victim: the company
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "could be accessed", "arguments": [{"name": "that data", "role": "compromised data"}, {"name": "Friday", "role": "time"}, {"name": "last week", "role": "time"}, {"name": "the company", "role": "victim"}, {"name": "customers", "role": "victim"}, {"name": "Saturday", "role": "time"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
He then used this backdoor to access various parts of the backend and dumped the private key used to generate the market 's .
|
data breach: dumped | attack pattern: used this backdoor | compromised data: private key
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "dumped", "arguments": [{"name": "private key", "role": "compromised data"}, {"name": "used this backdoor", "role": "attack pattern"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Most ransomware come with some sort of encryption key that is used to unlock the stolen data files once ransom is paid , though there is absolutely no guarantee that the perpetrator will keep their end of the bargain once money is transferred .
|
ransom: ransom is paid | tool: ransomware
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "ransom is paid", "arguments": [{"name": "ransomware", "role": "tool"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Patrick Wardle , director of research at Synack , echoed the same credential theory suggesting that breaches over the past year have given hackers ample opportunity to pull together some valid iCloud account credentials .
|
data breach: breaches | attacker: hackers | compromised data: credential | time: over the past year
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "breaches", "arguments": [{"name": "credential", "role": "compromised data"}, {"name": "over the past year", "role": "time"}, {"name": "hackers", "role": "attacker"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
On the surface , the dump — touted by Wikileaks as the biggest ever publication of confidential CIA documents — offers some explosive revelations .
|
data breach: the dump | attacker: Wikileaks | compromised data: confidential CIA documents
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "the dump", "arguments": [{"name": "Wikileaks", "role": "attacker"}, {"name": "confidential CIA documents", "role": "compromised data"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Finally today , the West Michigan Whitecaps - a Class A minor league baseball team affiliated with the Detroit Tigers - said staff W - 2 records were compromised after someone posing as a manager requested them .
|
phishing: posing as | attacker: someone | purpose: staff W - 2 records were compromised | trusted entity: a manager | victim: a Class A minor league baseball team
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "posing as", "arguments": [{"name": "someone", "role": "attacker"}, {"name": "a manager", "role": "trusted entity"}, {"name": "a Class A minor league baseball team", "role": "victim"}, {"name": "staff W - 2 records were compromised", "role": "purpose"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The business of ransomware has become so attractive that some cybercriminals do n’t even bother to actually encrypt the data , but just extort money from their victims with fake malware .
|
ransom: extort money | attack pattern: encrypt the data | attacker: cybercriminals | tool: fake malware | victim: their victims
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "extort money", "arguments": [{"name": "encrypt the data", "role": "attack pattern"}, {"name": "fake malware", "role": "tool"}, {"name": "cybercriminals", "role": "attacker"}, {"name": "their victims", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
In a ransomware attack , hackers inject a network with malware that typically encrypts important data , and then demand payment in exchange for a key that releases the data .
|
ransom: demand payment
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "demand payment", "arguments": []}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
All it takes is for one black hat to find a new zero - day networking software flaw and wide - spread ransomworm becomes a real possibility .
|
discover vulnerability: find | capabilities: wide - spread ransomworm | discoverer: one black hat | vulnerability: a new zero - day networking software flaw
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "find", "arguments": [{"name": "a new zero - day networking software flaw", "role": "vulnerability"}, {"name": "wide - spread ransomworm", "role": "capabilities"}, {"name": "one black hat", "role": "discoverer"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Recently the U.S. Computer Emergency Readiness Team issued an alert of phishing campaigns targeting airline consumers .
|
phishing: phishing campaigns | victim: airline consumers
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "phishing campaigns", "arguments": [{"name": "airline consumers", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Instead , stay prepared : Keep complete , disconnected backups of all systems , and periodically test that they can be restored , and thus never have to consider paying a ransom .
|
ransom: paying a ransom
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "paying a ransom", "arguments": []}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The hacking began on September 29th and continued at some locations for three months .
|
data breach: The hacking | time: September 29th | time: for three months
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "The hacking", "arguments": [{"name": "September 29th", "role": "time"}, {"name": "for three months", "role": "time"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
According to police , swindlers pretended to be friends of WhatsApp users and invented different excuses to lure them into revealing their account verification codes .
|
phishing: pretended to be | attacker: swindlers | trusted entity: friends | victim: WhatsApp users
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "pretended to be", "arguments": [{"name": "friends", "role": "trusted entity"}, {"name": "WhatsApp users", "role": "victim"}, {"name": "swindlers", "role": "attacker"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The group was behind the Poison Ivy malware family and has evolved its operations to include using custom tools capable of compromising high volumes of data from organisations and their customers , and stealthily moving it around the world .
|
data breach: compromising | attacker: The group | compromised data: data | tool: Poison Ivy malware | victim: organisations | victim: their customers
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "compromising", "arguments": [{"name": "data", "role": "compromised data"}, {"name": "organisations", "role": "victim"}, {"name": "their customers", "role": "victim"}, {"name": "The group", "role": "attacker"}, {"name": "Poison Ivy malware", "role": "tool"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
But as Cavallarin published details about it last week ( after not receiving any reply by the SquirrelMail developer ) , Golunski did the same during the weekend .
|
discover vulnerability: published | discoverer: Cavallarin | time: last week | vulnerability: it
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "published", "arguments": [{"name": "it", "role": "vulnerability"}, {"name": "last week", "role": "time"}, {"name": "Cavallarin", "role": "discoverer"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
However , Microsoft did not highlight the SMB flaw until April 14 , when a hacker group known as the Shadow Brokers released a set of exploits , allegedly stolen from the U.S.National Security Agency .
|
discover vulnerability: did not highlight | time: until April 14 | vulnerability: the SMB flaw | vulnerable system owner: Microsoft
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "did not highlight", "arguments": [{"name": "Microsoft", "role": "vulnerable system owner"}, {"name": "the SMB flaw", "role": "vulnerability"}, {"name": "until April 14", "role": "time"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
“ Given the huge attack surface , we found nearly 50 cybersecurity vulnerabilities in our initial research alone , ranging from insecure communications and authentication issues , to weak cryptography , memory corruption , and privacy problems , just to name a few ” .
|
discover vulnerability: found | discoverer: we | vulnerability: nearly 50 cybersecurity vulnerabilities
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "found", "arguments": [{"name": "nearly 50 cybersecurity vulnerabilities", "role": "vulnerability"}, {"name": "we", "role": "discoverer"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
" The danger of this information being leaked is that cybercriminals would have enough to engage in identity theft , obtain credit cards or even file a false tax return , " Diachenko writes .
|
data breach: being leaked | attack pattern: engage in identity theft | compromised data: this information | victim: cybercriminals
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "being leaked", "arguments": [{"name": "cybercriminals", "role": "victim"}, {"name": "this information", "role": "compromised data"}, {"name": "engage in identity theft", "role": "attack pattern"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The Exploitee.rs said they were motivated to look further at the cameras because of Samsung ’s response to their first disclosure .
|
discover vulnerability: their first disclosure | discoverer: The Exploitee.rs | vulnerable system owner: Samsung | vulnerable system: cameras
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "their first disclosure", "arguments": [{"name": "The Exploitee.rs", "role": "discoverer"}, {"name": "Samsung", "role": "vulnerable system owner"}, {"name": "cameras", "role": "vulnerable system"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
When reached Thursday , Lincoln Russell , a senior developer at Vanilla Forums stressed the vulnerabilities , which are in the middle of being fixed , only affect the company ’s free and open source product .
|
discover vulnerability: affect | vulnerable system owner: company | vulnerable system: free and open source product
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "affect", "arguments": [{"name": "company", "role": "vulnerable system owner"}, {"name": "free and open source product", "role": "vulnerable system"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The latest data dump comes less than 48 hours before France 's election , possibly too late to shift its outcome — at least to the degree that the hacks of the DNC and Clinton campaign chairman John Podesta did in the months leading up to the US election .
|
data breach: data dump | time: 48 hours
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "data dump", "arguments": [{"name": "48 hours", "role": "time"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The alleged list of email addresses and passwords appears to have been obtained from previously compromised third - party services .
|
data breach: previously compromised | victim: third - party services
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "previously compromised", "arguments": [{"name": "third - party services", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The hacker leaked the FBI.GOV accounts that he found in several backup files ( acc_102016 .
|
data breach: leaked | attacker: hacker | attacker: he | compromised data: FBI.GOV accounts | compromised data: backup files | number of data: several
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "leaked", "arguments": [{"name": "he", "role": "attacker"}, {"name": "hacker", "role": "attacker"}, {"name": "several", "role": "number of data"}, {"name": "backup files", "role": "compromised data"}, {"name": "FBI.GOV accounts", "role": "compromised data"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Discovered by a security researcher who goes by the name of Zenofex , these security flaws have not been reported to Western Digital , are still unpatched , and with public exploit code is available for more than half of the vulnerabilities .
|
patch vulnerability: are still unpatched | vulnerability: public exploit code | vulnerability: the vulnerabilities
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "patch vulnerability", "trigger": "are still unpatched", "arguments": [{"name": "the vulnerabilities", "role": "vulnerability"}, {"name": "public exploit code", "role": "vulnerability"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The Exploiteers published a proof - of - concept exploit that does just that .
|
discover vulnerability: published | discoverer: Exploiteers | vulnerability: proof - of - concept exploit
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "published", "arguments": [{"name": "Exploiteers", "role": "discoverer"}, {"name": "proof - of - concept exploit", "role": "vulnerability"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
We collect all data about your friends and family .
|
data breach: collect | attacker: We | attacker: friends and family | compromised data: data
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "collect", "arguments": [{"name": "We", "role": "attacker"}, {"name": "data", "role": "compromised data"}, {"name": "friends and family", "role": "attacker"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Once installed , Charger stole SMS contacts and prompted unsuspecting users to grant it all - powerful administrator rights .
|
data breach: stole | compromised data: SMS contacts | tool: Charger
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "stole", "arguments": [{"name": "SMS contacts", "role": "compromised data"}, {"name": "Charger", "role": "tool"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Recorded Future found the most references to CVE -2016-0189 , a vulnerability affecting Internet Explorer .
|
discover vulnerability: found | common vulnerabilities and exposures: CVE -2016-0189 | discoverer: Recorded Future | vulnerability: a vulnerability | vulnerable system: Internet Explorer
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "found", "arguments": [{"name": "Recorded Future", "role": "discoverer"}, {"name": "CVE -2016-0189", "role": "common vulnerabilities and exposures"}, {"name": "a vulnerability", "role": "vulnerability"}, {"name": "Internet Explorer", "role": "vulnerable system"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The bad news for the victims is that they will not be able to recover their files , even if they pay the ransom .
|
ransom: pay the ransom | victim: the victims | victim: they
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "pay the ransom", "arguments": [{"name": "the victims", "role": "victim"}, {"name": "they", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Their internet scans revealed hundreds of thousands of devices whose configurations could be changed remotely through the SNMP weakness that they found and dubbed StringBleed .
|
discover vulnerability: found | discoverer: they | vulnerability: StringBleed
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "found", "arguments": [{"name": "StringBleed", "role": "vulnerability"}, {"name": "they", "role": "discoverer"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
It ’s unknown how many accounts were compromised , or whether other applications are also involved .
|
data breach: were compromised | compromised data: accounts
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "were compromised", "arguments": [{"name": "accounts", "role": "compromised data"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The email 's subject line claims it 's a forwarded message about a flight confirmation , stating the airline , the destination , and the price of the flight .
|
phishing: claims | tool: The email #$%#s subject line | trusted entity: a forwarded message
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "claims", "arguments": [{"name": "The email #$%#s subject line", "role": "tool"}, {"name": "a forwarded message", "role": "trusted entity"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
According to researchers at Symantec Security Response , tracking ransom transactions would have been much more difficult if not for a bug in code that was supposed to create an individual bitcoin wallet for each victim : #WannaCry has code to provide unique bitcoin address for each victim but defaults to hardcoded addresses as a result of race condition bug — Security Response ( @threatintel ) May 16 , 2017 Because the code failed , it defaulted over the three preset wallets .
|
ransom: ransom | attack pattern: create an individual bitcoin wallet | victim: victim
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "ransom", "arguments": [{"name": "create an individual bitcoin wallet", "role": "attack pattern"}, {"name": "victim", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Nevertheless , in light of our EMV compliant point of sale systems , which rolled out last year , we believe the exposure to cardholder data that can be used to create counterfeit cards is limited , " it said .
|
data breach: exposure | compromised data: cardholder data
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "exposure", "arguments": [{"name": "cardholder data", "role": "compromised data"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
In a statement to the Senate Finance Committee , IRS chief John Koskinen said 35,000 affected people had been notified of the breach and $ 30 million been paid for around 8,000 fraudulent tax refunds .
|
data breach: the breach | damage amount: 30 million | number of victim: 35,000 | victim: people
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "the breach", "arguments": [{"name": "people", "role": "victim"}, {"name": "35,000", "role": "number of victim"}, {"name": "30 million", "role": "damage amount"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
That ’s a surprising design flaw for custom - made malware whose alleged objective was to collect and transmit location data on Ukrainian artillery to the GRU .
|
data breach: collect | attacker: GRU | compromised data: location data | tool: custom - made malware | victim: Ukrainian artillery
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "collect", "arguments": [{"name": "location data", "role": "compromised data"}, {"name": "Ukrainian artillery", "role": "victim"}, {"name": "GRU", "role": "attacker"}, {"name": "custom - made malware", "role": "tool"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
If an employee is working from home and gets hit by ransomware , it encrypts everything on the hard drive and demands payment in bitcoin to set data free .
|
ransom: gets hit | attack pattern: encrypts everything | tool: ransomware | victim: an employee | victim: hard drive
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "gets hit", "arguments": [{"name": "an employee", "role": "victim"}, {"name": "ransomware", "role": "tool"}, {"name": "encrypts everything", "role": "attack pattern"}, {"name": "hard drive", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The group is asking for either $ 75,000 in Bitcoin or $ 100,000 in iTunes gift cards before the April 7 deadline .
|
ransom: is asking for | attacker: The group | payment method: in Bitcoin | payment method: in iTunes gift cards | price: 100,000 | price: 75,000 | time: the April 7 deadline
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "is asking for", "arguments": [{"name": "the April 7 deadline", "role": "time"}, {"name": "in iTunes gift cards", "role": "payment method"}, {"name": "100,000", "role": "price"}, {"name": "75,000", "role": "price"}, {"name": "in Bitcoin", "role": "payment method"}, {"name": "The group", "role": "attacker"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
However , according to Facebook ’s representatives , this is n’t a vulnerability that has been exploited but a feature .
|
discover vulnerability: been exploited | vulnerability: vulnerability
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "been exploited", "arguments": [{"name": "vulnerability", "role": "vulnerability"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
With affected institutions including the Health Service Executive ( which said it prevented the ransomware from activating ) , the National Health Service in the UK , FedEx and PetroChina , few initially paid up , leading to speculation that organisations were taking their chances on fixing their corrupt machines before the ransom forced a mass deletion of critical data .
|
ransom: paid up | place: the UK | victim: FedEx | victim: PetroChina | victim: institutions | victim: the Health Service Executive | victim: the National Health Service
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "paid up", "arguments": [{"name": "the National Health Service", "role": "victim"}, {"name": "FedEx", "role": "victim"}, {"name": "the UK", "role": "place"}, {"name": "institutions", "role": "victim"}, {"name": "the Health Service Executive", "role": "victim"}, {"name": "PetroChina", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The presidential election commission said in statement that it would hold a meeting later on Saturday after Macron ’s campaign informed it about the hack and publishing of the data .
|
data breach: hack | compromised data: data
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "hack", "arguments": [{"name": "data", "role": "compromised data"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The vulnerability is similar to one disclosed by Vulnerability Lab and patched by Apple in iTunes and the App Store a year and a half ago .
|
discover vulnerability: disclosed | discoverer: Vulnerability Lab | vulnerability: The vulnerability
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "disclosed", "arguments": [{"name": "The vulnerability", "role": "vulnerability"}, {"name": "Vulnerability Lab", "role": "discoverer"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
More than one million Brits over the age of 45 have fallen victim to some form of email - related fraud , as the internet supersedes the telephone as the favored channel for scammers , according to Aviva .
|
phishing: email - related fraud | attacker: scammers | victim: Brits | victim: victim
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "email - related fraud", "arguments": [{"name": "scammers", "role": "attacker"}, {"name": "Brits", "role": "victim"}, {"name": "victim", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
A quick change in the settings on Word by customers would do the trick , but if Microsoft notified customers about the bug and the recommended changes , it would also be telling hackers about how to break in .
|
discover vulnerability: notified | vulnerability: the bug | vulnerable system owner: Microsoft
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "notified", "arguments": [{"name": "Microsoft", "role": "vulnerable system owner"}, {"name": "the bug", "role": "vulnerability"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
A separate Thales survey of 1,000 adults in the U.S. and the U.K. recently found that 55 percent of respondents would switch to only using cash at a retailer if they learned that credit card data had been stolen from its systems -- and 20 percent would stop shopping at that retailer altogether
|
data breach: been stolen | compromised data: credit card data | victim: its systems
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "been stolen", "arguments": [{"name": "its systems", "role": "victim"}, {"name": "credit card data", "role": "compromised data"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The bug was found by researchers Filippo Cavallarin and Dawid Golunski , independently of one another , and affects SquirrelMail versions 1.4.22 and below .
|
discover vulnerability: was found | discoverer: Dawid Golunski | discoverer: researchers Filippo Cavallarin | vulnerability: The bug | vulnerable system version: versions 1.4.22 | vulnerable system: SquirrelMail
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "was found", "arguments": [{"name": "researchers Filippo Cavallarin", "role": "discoverer"}, {"name": "Dawid Golunski", "role": "discoverer"}, {"name": "The bug", "role": "vulnerability"}, {"name": "SquirrelMail", "role": "vulnerable system"}, {"name": "versions 1.4.22", "role": "vulnerable system version"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
This greatly increases the likelihood that these vulnerabilities have been discovered by attackers to break into organization ’s SAP systems .
|
discover vulnerability: have been discovered | discoverer: attackers | vulnerability: these vulnerabilities | vulnerable system owner: organization | vulnerable system: SAP systems
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "have been discovered", "arguments": [{"name": "these vulnerabilities", "role": "vulnerability"}, {"name": "attackers", "role": "discoverer"}, {"name": "SAP systems", "role": "vulnerable system"}, {"name": "organization", "role": "vulnerable system owner"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
Cloudflare ’s inspection of tens of thousands of pages that were leaked from its reverse - proxy servers and cached by search engines revealed a " large number " of instances of internal Cloudflare cookies and headers .
|
data breach: were leaked | number of victim: tens of thousands | victim: its reverse - proxy servers | victim: pages
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "data breach", "trigger": "were leaked", "arguments": [{"name": "pages", "role": "victim"}, {"name": "tens of thousands", "role": "number of victim"}, {"name": "its reverse - proxy servers", "role": "victim"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
The attack attempts to trick users into handing over access to their email through fake Google third - party applications .
|
phishing: The attack
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "phishing", "trigger": "The attack", "arguments": []}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
That one demanded a $ 300 ransom paid in the form of mechanisms such as Paysafecard or uKash
|
ransom: demanded | price: 300
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "ransom", "trigger": "demanded", "arguments": [{"name": "300", "role": "price"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
EE
|
CASIE
|
train
|
Extract events and their components from the text. Format as 'event_type: trigger | role1: argument1 | role2: argument2'. Separate multiple events with '||'. Return 'None' if no events are identified.
|
A Samsung contact told Threatpost that the vulnerability affects only the SNH - 1011 model and it will be removed in an upcoming firmware update .
|
discover vulnerability: affects | discoverer: A Samsung | vulnerability: the vulnerability | vulnerable system: the SNH - 1011 model
|
Event types: patch vulnerability, treatment, data breach, phishing, ransom, discover vulnerability. Argument types: price, time, patch number, trusted entity, payment method, number of data, capabilities, tool, patch, supported platform, discoverer, release parole, vulnerable system, vehicle, vulnerability, vulnerable system owner, attack pattern, victim, damage amount, purpose, common vulnerabilities and exposures, place, releaser, compromised data, acquit, vulnerable system version, issues addressed, number of victim, attacker
|
ACE05: acquit, release parole, vehicle, place; PHEE: Treatment
|
{"events": [{"event_type": "discover vulnerability", "trigger": "affects", "arguments": [{"name": "A Samsung", "role": "discoverer"}, {"name": "the SNH - 1011 model", "role": "vulnerable system"}, {"name": "the vulnerability", "role": "vulnerability"}]}]}
|
You are an expert in Event Extraction.
Your task is to extract events and their arguments from the given text.
Follow these guidelines:
1. Identify event triggers and their types from the schema.
2. For each event, extract its arguments with their roles.
3. Format as 'event_type: trigger | role1: argument1 | role2: argument2' with events separated by '||'.
4. If no events are found, return 'None'.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.