At the time of writing the documentation on the TriggerFeed processor at kylo.io is ambiguous and insufficient. There are several problems:
it is not sufficiently clear that "Matching Execution Context Keys" is a list of prefixes for properties available in the global set of "execution context data" in the triggering feed
it is not stated that the chunk-of-json the dependent feed receives will have the parent "execution context data" for the triggering instance in the "latestFeedJobExecutionContext" leaf
the example JSON provided toward the bottom of the feed has no values in the "executionContext", so it is not clear what the format of the data is
there really should be an example JSONPath fragment corresponding to extracting a value from "latestFeedJobExecutionContext.executionContext"
it's not clear whether the example pointed at (a link to data_confidence_invalid_records.zip) is a NiFi template, or a kylo template, or how to examine the example.
Further to that, I would suggest that (and I am making a sweeping assumption about the format of the feed JSON):
then if the JSON that comes into the TriggerFeed is like this:
then the JsonPath would be something like