Theoretically this provides less collision resistance than straight SHA-512 hashing or straight PBKDF2 hashing. The reason is that if you can find a collision in either function, you can either make the input to SHA-512 the same or can (potentially, even though it's practically very hard) exploit the collision in SHA-512.
Practically however, collision resistance stays the same, which is "unbreakable", as we don't know a way to break SHA-512 in that regard, nor do we know how to break the collision resistance of PBKDF2.
As for password-hashing, the application which seems most likely here, the additional hash won't make the construction weaker, as you still have to do the 1M rounds of hashing to get to the relevant SHA-512 input. Note however that using PBKDF2 for password hashing is strongly discouraged in all but the most extreme cases due to much better and stronger alternatives like Argon2 and bcrypt being available.