Model-View-Controller
E182232
Model-View-Controller (MVC) is a software architectural pattern that separates an application into three interconnected components—model, view, and controller—to improve modularity, testability, and maintainability.
All labels observed (8)
| Label | Occurrences |
|---|---|
| Model-View-Controller canonical | 8 |
| MVC | 6 |
| Model-View-Controller pattern | 2 |
| Action Controller | 1 |
| Model–View–Controller | 1 |
| Model–View–Controller architectural pattern | 1 |
| Model–View–Controller pattern | 1 |
| model–view–controller (MVC) | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1610533 — 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: Model-View-Controller Context triple: [ASP.NET, supportsPattern, Model-View-Controller]
-
A.
MVC
MVC refers to the Missouri Valley Conference, one of the oldest NCAA Division I athletic conferences in the United States.
-
B.
Clean Architecture
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.
-
C.
Ruby on Rails
Ruby on Rails is a popular open-source web application framework that emphasizes convention over configuration and rapid development for building database-backed applications.
-
D.
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.
-
E.
Chain of Responsibility
Chain of Responsibility is a behavioral design pattern that decouples senders and receivers by passing a request along a chain of potential handlers until one of them processes it.
- 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: Model-View-Controller Target entity description: Model-View-Controller (MVC) is a software architectural pattern that separates an application into three interconnected components—model, view, and controller—to improve modularity, testability, and maintainability.
-
A.
MVC
MVC refers to the Missouri Valley Conference, one of the oldest NCAA Division I athletic conferences in the United States.
-
B.
Clean Architecture
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.
-
C.
Ruby on Rails
Ruby on Rails is a popular open-source web application framework that emphasizes convention over configuration and rapid development for building database-backed applications.
-
D.
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.
-
E.
Chain of Responsibility
Chain of Responsibility is a behavioral design pattern that decouples senders and receivers by passing a request along a chain of potential handlers until one of them processes it.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
design pattern
ⓘ
software architectural pattern ⓘ |
| abbreviation |
Model-View-Controller
self-linksurface differs
ⓘ
surface form:
MVC
|
| benefit |
clearer separation between UI and business logic
ⓘ
easier code maintenance ⓘ improved code reuse ⓘ |
| controllerResponsibility |
handle user input
ⓘ
interpret user actions ⓘ update model and view ⓘ |
| definesRoleOf |
Controller as input handler
ⓘ
Model as data and business logic ⓘ View as user interface representation ⓘ |
| domain |
software engineering
ⓘ
user interface design ⓘ |
| encourages |
high cohesion within components
ⓘ
loose coupling between components ⓘ |
| focusesOn | structuring interactive applications ⓘ |
| hasComponent |
Controller
ⓘ
Model ⓘ View ⓘ |
| implementedIn |
ASP.NET
ⓘ
surface form:
ASP.NET MVC
Django (loosely based) ⓘ Laravel ⓘ Ruby on Rails ⓘ Spring Framework ⓘ
surface form:
Spring MVC
|
| influenced | many web frameworks ⓘ |
| introducedBy | Trygve Reenskaug ⓘ |
| introducedInYear | 1979 ⓘ |
| modelResponsibility |
encapsulate business rules
ⓘ
manage application data ⓘ notify views of state changes ⓘ |
| originatedIn | Smalltalk community ⓘ |
| patternType | architectural pattern ⓘ |
| purpose |
improve maintainability
ⓘ
improve modularity ⓘ improve testability ⓘ separation of concerns ⓘ |
| relatedTo |
Model-View-Presenter
ⓘ
MVVM ⓘ
surface form:
Model-View-ViewModel
|
| supports |
parallel development of UI and logic
ⓘ
unit testing of business logic ⓘ |
| usedIn |
desktop applications
ⓘ
graphical user interface applications ⓘ mobile applications ⓘ web applications ⓘ |
| viewResponsibility |
display model state
ⓘ
provide user interface elements ⓘ render data to the user ⓘ |
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: Model-View-Controller Description of subject: Model-View-Controller (MVC) is a software architectural pattern that separates an application into three interconnected components—model, view, and controller—to improve modularity, testability, and maintainability.
Referenced by (21)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
MVC
this entity surface form:
Model–View–Controller
this entity surface form:
Model-View-Controller pattern
this entity surface form:
model–view–controller (MVC)
this entity surface form:
Action Controller
this entity surface form:
MVC
this entity surface form:
Model–View–Controller architectural pattern
this entity surface form:
MVC
this entity surface form:
MVC
this entity surface form:
Model–View–Controller pattern
this entity surface form:
MVC
this entity surface form:
Model-View-Controller pattern