You are on the right track. If you create Furniture interface, or base class, and have Table and Chair implement/extend that type, you should be good to go. You can then have a
List<Furniture>
for your House.
The only case where you would need to modify your mapping is if you want to implement any of the polymorphic mapping strategies outlined in the hibernate documentation. Some options are
to create a Furniture table and have all Chairs/Tables in that table instead (One table per class hierarchy). You do not have to do this. In this case your table would have all the properties of both classes, so not all columns would be used depending on the type being persisted. There would be a 'discriminator' column so hibernate could tell the type of a row.
You want to create a Furniture table, and refactor/normalize your Table/Chair tables so that all common fields are pulled into the Furniture table. You keep the Table and Chair tables. This is another type of polymorphic mapping (check the docs)
Other options in the hibernate docs.
Option 1 is the preferred strategy in the hibernate docs, I believe.
But to get down to it, you don't have to do any of these -- your entities can extend/inherit from other types without any special mapping considerations, if you are willing to have the duplicate columns in the tables.
I would write some simple JUnit or whatever tests and try it out.