The first time I saw these I remember thinking what is going on here. It can be pretty foreign the first time someone sees it especially coming from Cisco IOS. The two CLIs wrap and abstract the underlying standardized frameworks pretty differently. I think it helps to decouple what the function of the table is before ever operating the gear. I tended to start banging away on the gear and wind up with holes since I didn’t breakdown the architectural pieces first. It would have saved many days of back tracking if I had started with a clear breakdown of the tables and still does to this day
JUNOS maintains various tables routing tables. Most are default names that cannot be changed except for routing-instance prepends e.g. <routing-instance-name>.inet.0. I threw together some examples of what the output looks like.
Below are examples of the CLI output from some of these tables from a Juniper MX960.