While the display is bit confusing, what you are seeing is completely normal.
Just some clarifications. With the APFS file system Apple now uses, a container is what was traditionally called a physical partition. Now Volumes are subdivisions of that container. While they are somewhat related to what was once called a partition, they are not fixed in size and can grow as needed within the container. Basically they are more analogous to a special directory that only APFS can manage at a very basic disk level.
Broken down somewhat clearer in Terminal, the actual physical drive looks like this:
/dev/disk0 (internal, physical):
  #:            TYPE NAME          SIZE    IDENTIFIER
  0:   GUID_partition_scheme            *500.3 GB  disk0
  1:       Apple_APFS_ISC Container disk1     524.3 MB  disk0s1
  2:       Apple_APFS Container disk3     494.4 GB  disk0s2
  3:    Apple_APFS_Recovery Container disk2     5.4 GB   disk0s3
#1 and #3 are special containers (partitions in old speak) used for booting and recovery.
/dev/disk3 (synthesized):
  #:            TYPE NAME          SIZE    IDENTIFIER
  0:   APFS Container Scheme -           +494.4 GB  disk3
                 Physical Store disk0s2
  1:        APFS Volume Macintosh HD      10.3 GB  disk3s1
  2:        APFS Volume Preboot         7.6 GB   disk3s2
  3:        APFS Volume Recovery        937.2 MB  disk3s3
  4:        APFS Volume Data          122.4 GB  disk3s5
  5:  APFS Volume VM           1.1 GB   disk3s6
This is the volume structure of "Apple_APFS Container disk3". All needed by the Mac. #4, APFS Volume Data, contains all the apps, data, user directories, and a working version of macOS. All the others are needed by macOS or by APFS and have no connection to the user.
So, bottom line, all those items are needed and absolutely necessary and should not ever be messed with other than the instance of reformatting the entire drive in preparations to install macOS.