{"instruction": "You are an expert in event extraction. Please extract events from the input that conform to the schema definition. Return an empty list for events that do not exist, and return NAN for arguments that do not exist. If an argument has multiple values, please return a list. Respond in the format of a JSON string.", "schema": [{"event_type": "phishing", "trigger": true, "arguments": ["damage amount", "attacker", "time", "victim", "tool", "purpose", "attack pattern", "trusted entity", "place"]}, {"event_type": "discover vulnerability", "trigger": true, "arguments": ["vulnerable system", "vulnerable system owner", "common vulnerabilities and exposures", "vulnerable system version", "time", "discoverer", "capabilities", "supported platform"]}, {"event_type": "patch vulnerability", "trigger": true, "arguments": ["vulnerable system version", "issues addressed", "vulnerability", "patch", "patch number", "releaser", "supported platform", "vulnerable system"]}, {"event_type": "ransom", "trigger": true, "arguments": ["price", "damage amount", "time", "place", "payment method", "attacker", "attack pattern"]}, {"event_type": "data breach", "trigger": true, "arguments": ["compromised data", "number of victim", "attacker", "place", "damage amount", "purpose", "victim", "tool", "number of data", "attack pattern"]}], "input": "\" Because financial institutions do n’t send customer details in emails , the premise is that users will be more inclined to click on a link or open an attachment if it claims to be a secure or important message . \""}
{"phishing": [{"trigger": "claims to be", "arguments": {"damage amount": "NAN", "attacker": "NAN", "time": "NAN", "victim": "users", "tool": "NAN", "purpose": "NAN", "attack pattern": "click on a link or open an attachment", "trusted entity": "a secure or important message", "place": "NAN"}}], "discover vulnerability": [], "patch vulnerability": [], "ransom": [], "data breach": []}