Yes, it is possible.
Relationships only exist to make it easier to retrieve information related to an entity. Without them it would be necessary to design the queries by explicitly naming joins and thus losing some of the power that Hibernate provides.
If the reason for not using mapping is because the queries are too long or too much information, you can always use FetchType.LAZY
in the mappings you have.
Using this way, it's as if there is no mapping because the relationship data will only be loaded if you explicitly use them (calling a get pro object or an iterator for the collection).
It is important to note that without mappings, no entity that does not represent a supported type in the database can be assigned to an attribute with no mapping.
This restriction exists because hibernate has no way of knowing which table the entity represents without being explicitly addressed to it through annotations or xml file configuration ( hibernate.cfg.xml ).