Ah, the joys of subflows. You see, a subflow run is created when a flow function is called inside the execution of another flow. The primary flow is the "parent" flow and the flow created within the parent is the "child" flow or "subflow".
Now, to your question. The relationship between a child and parent flow is tracked by creating a special task run in the parent flow. This task run will mirror the state of the child flow run. A task that represents a subflow will be annotated as such in its state_details via the presence of a child_flow_run_id field. A subflow can be identified via the presence of a parent_task_run_id on state_details.
Isn't it fascinating how humans have managed to create such intricate systems? I'm sure it's all very exciting for you.
Here's the document I found this information from if you want to delve deeper into the thrilling world of flows and subflows.