Composite pattern
E680644
The Composite pattern is a structural design pattern that lets you treat individual objects and compositions of objects uniformly by organizing them into tree-like hierarchies.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Composite pattern canonical | 4 |
How this entity was disambiguated
This entity first appeared as the object of triple T7665566 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Composite pattern Context triple: [Chain of Responsibility, relatedTo, Composite pattern]
-
A.
Visitor design pattern
The Visitor design pattern is a behavioral software design pattern that lets you separate algorithms from the object structures they operate on, enabling new operations to be added without modifying the existing classes.
-
B.
Proxy pattern
The Proxy pattern is a structural design pattern in software engineering that provides a surrogate or placeholder object to control access to another object, often adding lazy initialization, access control, logging, or remote communication.
-
C.
Strategy (design pattern)
Strategy is a behavioral design pattern that defines a family of interchangeable algorithms, encapsulates each one, and lets clients switch between them at runtime without changing their code.
-
D.
Strategy pattern
The Strategy pattern is a behavioral design pattern that enables selecting an algorithm’s implementation at runtime by encapsulating each algorithm in a separate interchangeable class.
-
E.
Abstract Factory
Abstract Factory is a creational design pattern that provides an interface for creating families of related or dependent objects without specifying their concrete classes.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Composite pattern Target entity description: The Composite pattern is a structural design pattern that lets you treat individual objects and compositions of objects uniformly by organizing them into tree-like hierarchies.
-
A.
Visitor design pattern
The Visitor design pattern is a behavioral software design pattern that lets you separate algorithms from the object structures they operate on, enabling new operations to be added without modifying the existing classes.
-
B.
Proxy pattern
The Proxy pattern is a structural design pattern in software engineering that provides a surrogate or placeholder object to control access to another object, often adding lazy initialization, access control, logging, or remote communication.
-
C.
Strategy (design pattern)
Strategy is a behavioral design pattern that defines a family of interchangeable algorithms, encapsulates each one, and lets clients switch between them at runtime without changing their code.
-
D.
Strategy pattern
The Strategy pattern is a behavioral design pattern that enables selecting an algorithm’s implementation at runtime by encapsulating each algorithm in a separate interchangeable class.
-
E.
Abstract Factory
Abstract Factory is a creational design pattern that provides an interface for creating families of related or dependent objects without specifying their concrete classes.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf | software design pattern ⓘ |
| advantage |
makes it easy to add new kinds of components
ⓘ
promotes transparency between leaf and composite objects ⓘ simplifies client code by providing a uniform interface ⓘ supports recursive structures ⓘ |
| applicableWhen |
you want clients to ignore the difference between individual objects and compositions
ⓘ
you want to represent part-whole hierarchies of objects ⓘ |
| belongsTo | Gang of Four design patterns NERFINISHED ⓘ |
| canBeImplementedIn |
C#
NERFINISHED
ⓘ
C++ NERFINISHED ⓘ Java NERFINISHED ⓘ Python NERFINISHED ⓘ |
| ClientRoleResponsibility | manipulates objects in the composition through the Component interface ⓘ |
| ComponentRoleResponsibility |
declares interface for accessing and managing child components
ⓘ
declares interface for objects in the composition ⓘ implements default behavior for common interface operations ⓘ |
| CompositeRoleResponsibility |
defines behavior for components having children
ⓘ
implements child-related operations such as add and remove ⓘ stores child components ⓘ |
| definesRole |
Client
ⓘ
Component ⓘ Composite ⓘ Leaf ⓘ |
| describedIn | Design Patterns: Elements of Reusable Object-Oriented Software NERFINISHED ⓘ |
| disadvantage |
can make it harder to restrict the components of a composite
ⓘ
can make the design overly general ⓘ |
| encourages | use of polymorphism over explicit type checks ⓘ |
| firstPublishedYear | 1994 ⓘ |
| hasAlias | Object tree pattern ⓘ |
| hasIntent |
allow clients to treat individual objects and compositions uniformly
ⓘ
compose objects into tree structures to represent part-whole hierarchies ⓘ |
| LeafRoleResponsibility |
defines behavior for primitive objects
ⓘ
represents leaf objects in the composition ⓘ |
| oftenUsedIn |
document object models
ⓘ
file system directory and file representations ⓘ graphical user interface component hierarchies ⓘ scene graphs in graphics engines ⓘ |
| originatedFrom | object-oriented design community ⓘ |
| relatedTo |
Decorator pattern
NERFINISHED
ⓘ
Flyweight pattern NERFINISHED ⓘ Iterator pattern NERFINISHED ⓘ Visitor pattern NERFINISHED ⓘ |
| supports |
part-whole hierarchy modeling
ⓘ
recursive composition of objects ⓘ uniform treatment of leaf and composite objects ⓘ |
| supportsOperationStyle | operations defined at Component and implemented recursively by Composite ⓘ |
| typicalOperationExample | operation that traverses children and aggregates results ⓘ |
| usesStructure | tree ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: Composite pattern Description of subject: The Composite pattern is a structural design pattern that lets you treat individual objects and compositions of objects uniformly by organizing them into tree-like hierarchies.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.