As a extension: from a DB perspective, if a chuck of info is someting that you would logically normalize into its own table, does that suggest that it should be its own object?

Not necessarily. I think that an object (like a person) will often be implemented across many tables, depending on roles and relationships that apply to that person. I generally try to keep the database implementation details quite separate from the object implementation.