I might be wrong, but you could have a column called PhoneEntity so you can know which table uses that phone.

Your "single table model" suggests a phone can be owned by more than one person and (the following you said it happened) a person can have more than one phone.

The design relies on many things and the most common (and correct) answer is "it depends".

The "multiple table model" could generate some duplicates and could multiply your work trying to administer the tables. Other than that, it could be better for performance.

I would like to know what others more experienced have to say. This could be used for addresses as well.