The triggered pipeline actually runs as the user who created the task, so the information shown in the dashboard is accurate. The pipeline has to run as the task creator to ensure that the execution has access to any other resources/assets required for the execution. Running the pipeline as the task invoker can cause permission errors if the invoker has lesser privileges than the creator.
There is already an enhancement request open for showing the invoker id in addition to the task creator. The additional information can be added if the invocation is done using an user account, it cannot be shown when the invocation is done using a bearer token.