Empty GOs as info storage

Having Unity create an empty GO just to use its name to define some sort of behavior is huge overkill and a quite odd way to go about solving this, I think. :) Like save pointed out in the above, you're not making individual scripts for each combination. Instead, you're setting variables in each script instance to represent the characteristics of that particular building.

Here's the general idea, more elaborately explained:

1. Define a GameObject called "Building".

2. Make a script called "BuildingScript" or something, and attach it to the Building GO.

3. In the script, define all the booleans, floats, strings, etc. that make up the characteristics that define a building.

4. In the script, define a method that takes an argument describing the building type, and then initializes the building's variables to some particular preset based on that argument.

5. Make an empty prefab, and drag the Building GameObject onto it, to make a general Building Prefab, then delete the Building GameObject. Now you have a Building prefab, each clone of which is going to instantiate with its own instance of BuildingScript.

6. When you instantiate clones of the Building prefab, call the method that initializes its variables with an argument that defines what particular building type you want this clone to be.

You didn't mention which programming language you're using, so I'm going to take the liberty to choose C# for the example. ;) Hope it's alright, if not, I'm sure you can translate it to whatever you use. Here's what the BuildingScript could look like:

 using UnityEngine;
 using System.Collections;
 
 public class BuildingScript : MonoBehaviour {
 
     public bool CanBeInDoor { get; set; }
     public bool ShouldBeStackedOnOtherBuilding { get; set; }
     public bool IsTheBabelTower { get; set; }
     public bool EifelWouldBeProud { get; set; }
 
     public void Initialize(string buildingType)
     {
         switch (buildingType)
         {
             case "Babel":
                 CanBeInDoor = false;
                 ShouldBeStackedOnOtherBuilding = false;
                 IsTheBabelTower = true;
                 EifelWouldBeProud = true;
                 break;
             case "EmpireState":
                 CanBeInDoor = false;
                 ShouldBeStackedOnOtherBuilding = false;
                 IsTheBabelTower = false;
                 EifelWouldBeProud = true;
                 break;
             case "HumbleHut":
                 CanBeInDoor = false;
                 ShouldBeStackedOnOtherBuilding = true;
                 IsTheBabelTower = false;
                 EifelWouldBeProud = false;
                 break;
             case "NonLivableDwelling":
                 CanBeInDoor = true;
                 ShouldBeStackedOnOtherBuilding = true;
                 IsTheBabelTower = false;
                 EifelWouldBeProud = false;
                 break;
             case "DollHouse":
                 CanBeInDoor = true;
                 ShouldBeStackedOnOtherBuilding = false;
                 IsTheBabelTower = false;
                 EifelWouldBeProud = false;
                 break;
             default:
                 break;
         }
     }
 }

Here is what it would look like when you instantiate buildings:

 public class ThisIsSomeOtherScript : MonoBehaviour
 {
     public Transform BuildingPrefab; // Drag the prefab onto this variable in the editor
 
     void CreateTwoCopies()
     {
         Transform dollHouseInstance = (Transform)Instantiate(BuildingPrefab);
         dollHouseInstance.GetComponent<BuildingScript>().Initialize("DollHouse"); // This now has all of DollHouse's characteristics
 
         Transform empireStateInstance = (Transform)Instantiate(BuildingPrefab);
         empireStateInstance.GetComponent<BuildingScript>().Initialize("EmpireState"); // This now has all of EmpireState's characteristics
     }
 }