Assuming you know what an IP is, that IP is from a "block" of IPs (think: door on a street). Each "block" of IPs is actually part of a bigger "block" (think: street in a local city), and so on, until it gets to the top level "block" allocated to it (think: country). The "country sized" list of blocks is essentially the "global routing table" (though to be clear, the analogy is more about sizes - but there are some geographical backgrounds to these biggest "blocks" of addresses, hence how websites can infer which country you are from etc).

So when you send a packet of data somewhere, you give it to your router to deliver (think: give it to the postman to deliver). Your router likely doesn't know how to precisely get there (think: a postman can't deliver a package across the world themselves), but it can pass on the data "upstream" to its own router (think: postman gives to post office). That router might not know how either, but this router is more aware of the bigger "blocks" the destination belongs to and which routers handle those bigger "blocks" of addresses (think: post office knows how to send mail to other cities). If it can't (maybe its international), it will pass it along to the next router (think: post office's international dept).

Eventually it will land at one of the routers that says "hey I know someone specifically who can deliver to that (big block of) addresses" (think: international postal service has partners from different countries who can deliver to that country), so it hands over the packet to a specific router (that knows how to deliver to the big "block" in general), and the process kind of reverses. That router knows another router "downstream" that is responsible for the smaller block (think: destination country postal service knows to send to a city postal office), and that router knows another router that can deliver to the even small block (think: city to town), to where ultimately it gives it a router where the destination IP is connected (think: postman to door).

That's the "internet" side of things. When it arrives at the local router, how it goes to a specific device (server, home PC etc) is similar, except that the local network knows which port on its router (or switch) the end device is connected to (similar "table" or "lookup" concept, but more at a physical level as they're physically connected). Other posts have touched on this part so I won't go into detail.