TTFB is quite an overloaded term and it can be confusing.
In terms of the CrUX data, TTFB refers to the TTFB of the original document request (
including any redirects). This of this as page-level TTFB and it's an important metric as, until you get the page, you can't meet the other metrics, or load any other resources needed for them (CSS, Scripts, Images...etc.).
TTFB can also be measured on each resource - how long from the request of that resource until you get the first byte of that resource back. This can be useful to measure any latency in individual resources. For example if your LCP element is an image and you see it's slow despite the page having a fast TTFB and the LCP element being discoverable in that, then maybe it's due to a slow TTFB of that resource (which could be due to being on another domain, like an image CDN and thus requiring a new TCP/TLS connection).
But in general, when discussing TTFB in terms of web performance, it refers to the first bytes of the HTML document.