I can't speak for the Enterprise Security app v2.0, but in the prior version, there is no direct link between notable events and the events correlation searches found that triggered them. In other words, the way the app had been designed previously was a one-way data flow: correlation_search(event)=>notable_event. Out of box, no two-way.
I would think the next best thing you can possibly do is to populate a new lookup with keys from notable events and other fields to keys to identify original events.
If you assembled keys based on throttle time and signature against which you can check new notable events, just append there.
