Roughly, e.g.: 1:Fiber, 2:Ethernet, 3:Routing, 4:TCP/IP, and 7:HTTP.
4 and 7 are ceasing to be real - HTTP2 is both a session protocol and an application protocol, and that's before we even get into things like DoH.
The model is still solid, even if the most common implementation has melted a bit.
I do think it is useful as an architectural device or a conceptual design goal -- i.e. a model to model your models on. :)
But I also concede that part of its teaching value is that it is a failure in practice.
It was a formalization of the ad hoc (successful!) design strategies of early networking. I see echoes of it everywhere, most obviously in the Linux kernel, and I think it's valuable for that.
The usual criticism of the OSI model is that there are grey areas and dependencies, where a lower layers bleed into higher layers (e.g. L2 switching which can work a lot like routing in modern hardware), and higher layers that are tightly bound to lower layers, making the distinctions unclear.
The purist in me wants to agree, but I think the model is too useful to disregard casually.
The value comes from the abstraction, and like Newtonian physics, it is a great model -- until it isn't.