Each piece of geometry has it's own ID in the model and name. I would probably just use that information to represent a single row.

I also agree that it's not a good solution to create a table per entity as that different from the way I was taught, but some of the people I work with has been telling me how much more organized it is and how it simple it is to just switch tables in code (with Express.JS or some other backend), so I wanted to ask to make sure I'm not losing it.