What advantages do you see in that additional table?
I'd keep the basic info for both in one table, but would split off the phone number data into a related table so that I can link a flexible number of phone numbers to the same person. I often put email addresses in the same table using the same field for both phone and email addresses, but with an added "label" field with a value list of values such as "home", "fax", "business", "cell", "email".... to tell the user which is which.
But the devil is in the details and that's not something that you've yet chosen to share in this discussion.
a second table is ideal. Why - even if there is little duplication, there is some duplication and should be avoided. If a PTN gets a new phone number, it only needs to be updated in one record, no matter how many times it is referenced by an address record. That's the main reason. Other than that, it's standard practice. The downside is that you need to manage the relationship and anticipate when new data entries match existing entries.
Are you sure that you really meant to say that a "second table is ideal"? The rest of your table appears to say the exact opposite.
I see Address---<PTN
and since people and their phone numbers are not necessarily attached to an address, I'd want to separate the two. Maybe I simply misunderstand the problem.
Of course, it could actually be Address>---<PTN.
No I think that I misunderstood you and that you have a better grasp of the issue than I did...
(edit ... pshaw has multiple definitions - mine wasn't disdain or contempt, just disbelief.)