In order to model multiple split AC units within one zone, you'll have to get away from using HVACTemplate objects. These are the big-ticket objects you'll need for your model:

• ZoneHVAC:PackagedTerminalAirConditioner (if your split units have heating and cooling) or ZoneHVAC:WindowAirConditioner (if your split units have cooling only). Both of these objects contain an outdoor air mixer and fan along with the DX cooling coil.
• ZoneHVAC:EquipmentList: object lists all HVAC equipment connected to a zone, as well as the priority of each equipment in heating and cooling.
• ZoneHVAC:EquipmentConnections: defines the ZoneHVAC:EquipmentList object connected to a zone, as well as names of the zone's air node, inlet node, exhaust node, and return node

Note that you will need to define lots of other objects to have your model run successfully (the cooling coil, fan, outdoor air mixer, thermostat, etc.). As Julien mentioned in his answer, you can use the expidf file to see these underlying objects created from the HVACTemplate objects. The links I included are for documentation of v8.3 of EnergyPlus, but when I compare the IDD file for the objects above between v8.3 and v8.4 the only difference of interest is that there are some new input fields at the end of ZoneHVAC:EquipmentConnections in v8.4 that can modify return air flow back to a central air system.

If you do have a central air system (roof top air handler, DOAS unit, etc.), the HVACTemplate:System:Unitary object will only create a system that is constant volume with DX cooling and your choice of heating. If this doesn't match your building, you will need to also create the air loop from scratch.