It is still advised to use SQL for such use-case, as @jake314159 suggested already. Here you can find a step-by-step explanation of his suggestion and a bit more on top.
Additionally, there is a similar question has been asked some time ago and there you find a way how to manually map
TriggeredSendExternalKey and identify what was the journey used for sending.
There is no special option to add the
Journey Name field to the Tracking Extract's file. Maybe the only thing to try is to set some field that you would receive in the file that would include Journey's name, e.g.
EmailName field from SendJob would have a naming pattern like -
[Journey_Name]_Email_#1. but then you would need to make sure that you are not re-using emails across different journeys.