Well Hibernate does suggest a pattern called "table per class hierarchy" which uses a discriminator column to tell Hibernate which type or object a row represents. Have a look in the docs, they cover this.
In my opinion, its an anti-pattern. Fine, it fixes what would be a slightly odd bit of OO modelling, but only by introducing poor modelling in your ER model (you have to introduce nullable properties for data that should never be null for example). My experience of database backed applications is that the data model is key, so don't weaken it lightly.