In data modeling, which type of entity represents a logical template or generalization whose real-world occurrences are represented by a second, associated entity?

Introduction / Context:
Designs sometimes distinguish between a blueprint and its concrete occurrences. This pattern clarifies how templates (archetypes) relate to their realized instances in databases.

Given Data / Assumptions:

• An entity serves as a logical generalization or template.
• Another entity records actual occurrences tied back to the template.
• We need the name of the template entity.

Concept / Approach:
The archetype/instance pattern models two related entities: an Archetype (template) that defines default or canonical characteristics, and an Instance that represents a real occurrence. This differs from supertype/subtype, which models specialization within a single generalization hierarchy.

Step-by-Step Solution:

Verification / Alternative check:
Examples: ProductTemplate (archetype) and ProductItem (instance); ContractType (archetype) and Contract (instance).

Why Other Options Are Wrong:

• Supertype and subtype describe inheritance hierarchies within one concept, not template-to-occurrence pairing.
• Instance entity describes the occurrence itself, not the template.

Common Pitfalls:
Confusing supertype/subtype with archetype/instance. The first is about specialization; the second is about template versus occurrence.

Final Answer:
Archetype entity