Inheritance is an "is a" relationship; employee is a person, so an employee's id is a person's id. If you're using table per concrete class mapping as Rippo suggested, then the Employee table should have a primary key of PersonId that is also a foreign key to the Person table.
I would also think about modeling this relationship using roles instead of inheritance.