{"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": ["time", "trusted entity", "victim", "attacker", "place", "tool"]}, {"event_type": "discover vulnerability", "trigger": true, "arguments": ["supported platform", "vulnerable system version", "discoverer", "vulnerable system", "capabilities", "vulnerability", "common vulnerabilities and exposures", "time"]}, {"event_type": "ransom", "trigger": true, "arguments": ["damage amount", "victim", "place", "attacker", "price", "tool"]}, {"event_type": "patch vulnerability", "trigger": true, "arguments": ["vulnerable system", "supported platform", "patch number", "patch", "vulnerability", "releaser", "common vulnerabilities and exposures", "vulnerable system version"]}], "input": "Thus , if a chip family falls under one of those categories – such as Intel ca n't easily fix Spectre v2 in the design , or customers do n't think the hardware will be exploited – it gets a \" stopped \" sticker ."}
{"phishing": [], "discover vulnerability": [], "ransom": [], "patch vulnerability": [{"trigger": "fix", "arguments": {"vulnerable system": "NAN", "supported platform": "NAN", "patch number": "NAN", "patch": "NAN", "vulnerability": "Spectre v2", "releaser": "Intel", "common vulnerabilities and exposures": "NAN", "vulnerable system version": "NAN"}}]}