Clean Architecture
E173638
Clean Architecture is a software design philosophy and set of principles, popularized by Robert C. Martin, that emphasizes separation of concerns, testability, and independence from frameworks, databases, and user interfaces.
All labels observed (4)
| Label | Occurrences |
|---|---|
| Clean Architecture: A Craftsman’s Guide to Software Structure and Design | 5 |
| Clean Architecture canonical | 3 |
| Clean Architecture book | 1 |
| Clean Architecture by Uncle Bob | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1531676 — 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: Clean Architecture Context triple: [Clean Code: A Handbook of Agile Software Craftsmanship, relatedWork, Clean Architecture]
-
A.
Clean Code: A Handbook of Agile Software Craftsmanship
Clean Code: A Handbook of Agile Software Craftsmanship is a highly influential software engineering book by Robert C. Martin that teaches principles and practices for writing readable, maintainable, and high-quality code.
-
B.
Domain-Driven Design: Tackling Complexity in the Heart of Software
"Domain-Driven Design: Tackling Complexity in the Heart of Software" is a seminal software engineering book by Eric Evans that introduces the domain-driven design approach for managing complexity in large, business-focused software systems.
-
C.
Design Patterns: Elements of Reusable Object-Oriented Software
Design Patterns: Elements of Reusable Object-Oriented Software is a seminal software engineering book by the "Gang of Four" that catalogues foundational object-oriented design patterns widely used in software development.
-
D.
Refactoring: Improving the Design of Existing Code
"Refactoring: Improving the Design of Existing Code" is a seminal software engineering book by Martin Fowler that systematically defines refactoring techniques to improve code structure while preserving behavior.
-
E.
360 Architecture
360 Architecture was a Kansas City–based architectural firm known for designing major sports venues and large-scale entertainment facilities, including MetLife Stadium.
- 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: Clean Architecture Target entity description: Clean Architecture is a software design philosophy and set of principles, popularized by Robert C. Martin, that emphasizes separation of concerns, testability, and independence from frameworks, databases, and user interfaces.
-
A.
Clean Code: A Handbook of Agile Software Craftsmanship
Clean Code: A Handbook of Agile Software Craftsmanship is a highly influential software engineering book by Robert C. Martin that teaches principles and practices for writing readable, maintainable, and high-quality code.
-
B.
Domain-Driven Design: Tackling Complexity in the Heart of Software
"Domain-Driven Design: Tackling Complexity in the Heart of Software" is a seminal software engineering book by Eric Evans that introduces the domain-driven design approach for managing complexity in large, business-focused software systems.
-
C.
Design Patterns: Elements of Reusable Object-Oriented Software
Design Patterns: Elements of Reusable Object-Oriented Software is a seminal software engineering book by the "Gang of Four" that catalogues foundational object-oriented design patterns widely used in software development.
-
D.
Refactoring: Improving the Design of Existing Code
"Refactoring: Improving the Design of Existing Code" is a seminal software engineering book by Martin Fowler that systematically defines refactoring techniques to improve code structure while preserving behavior.
-
E.
360 Architecture
360 Architecture was a Kansas City–based architectural firm known for designing major sports venues and large-scale entertainment facilities, including MetLife Stadium.
- F. None of above. chosen
Statements (55)
| Predicate | Object |
|---|---|
| instanceOf |
architectural pattern
ⓘ
software architecture style ⓘ software design philosophy ⓘ |
| alsoKnownAs |
Clean Architecture
ⓘ
surface form:
Clean Architecture by Uncle Bob
|
| category |
software architecture
ⓘ
software design patterns and principles ⓘ software engineering ⓘ |
| coreConcept |
dependency rule
ⓘ
entities as enterprise business rules ⓘ frameworks and drivers ⓘ interface adapters ⓘ layers of software ⓘ use cases as application core ⓘ |
| creator | Robert C. Martin ⓘ |
| dependencyDirection | source code dependencies point inwards ⓘ |
| describedIn |
Clean Architecture
self-linksurface differs
ⓘ
surface form:
Clean Architecture: A Craftsman’s Guide to Software Structure and Design
blog posts by Robert C. Martin ⓘ |
| emphasizes |
independence from databases
ⓘ
independence from external agencies ⓘ independence from frameworks ⓘ independence from user interfaces ⓘ separation of concerns ⓘ testability ⓘ |
| goal |
ease of change
ⓘ
flexibility ⓘ independence from infrastructure ⓘ long-term sustainability of software ⓘ maintainability ⓘ testability ⓘ |
| hasLayer |
entities layer
ⓘ
frameworks and drivers layer ⓘ interface adapters layer ⓘ use cases layer ⓘ |
| influencedBy |
Clean Code principles
ⓘ
Hexagonal Architecture ⓘ Onion Architecture ⓘ SOLID principles ⓘ Screaming Architecture ⓘ |
| promotes |
UI-agnostic design
ⓘ
boundary separation ⓘ database-agnostic design ⓘ dependency inversion principle ⓘ framework-agnostic design ⓘ inversion of control ⓘ test-first or testable design ⓘ use-case driven design ⓘ |
| recommends |
business rules independent of UI
ⓘ
business rules independent of database ⓘ business rules independent of external services ⓘ defining boundaries via interfaces ⓘ isolating side effects at the outer layers ⓘ |
| usedFor |
enterprise applications
ⓘ
microservices ⓘ mobile applications ⓘ web applications ⓘ |
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: Clean Architecture Description of subject: Clean Architecture is a software design philosophy and set of principles, popularized by Robert C. Martin, that emphasizes separation of concerns, testability, and independence from frameworks, databases, and user interfaces.
Referenced by (10)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
Clean Architecture: A Craftsman’s Guide to Software Structure and Design
subject surface form:
Robert C. Martin
this entity surface form:
Clean Architecture book
subject surface form:
Robert C. Martin
this entity surface form:
Clean Architecture: A Craftsman’s Guide to Software Structure and Design
this entity surface form:
Clean Architecture: A Craftsman’s Guide to Software Structure and Design
this entity surface form:
Clean Architecture: A Craftsman’s Guide to Software Structure and Design
this entity surface form:
Clean Architecture by Uncle Bob
this entity surface form:
Clean Architecture: A Craftsman’s Guide to Software Structure and Design