Model-View-Presenter
E827354
Model-View-Presenter is a software architectural pattern that separates an application into model, view, and presenter components to improve testability and maintainability, particularly in user interface code.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Model-View-Presenter canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T9898517 — 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-Presenter Context triple: [Model-View-Controller, relatedTo, Model-View-Presenter]
-
A.
Model-View-Controller
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.
-
B.
MVC
MVC refers to the Missouri Valley Conference, one of the oldest NCAA Division I athletic conferences in the United States.
-
C.
MVVM
MVVM (Model–View–ViewModel) is a software architectural pattern that separates an application's user interface from its business logic and data models to improve testability, maintainability, and modularity.
-
D.
Model Driven Architecture
Model Driven Architecture is a software design approach defined by the Object Management Group that focuses on creating platform-independent models which can be systematically transformed into platform-specific implementations.
-
E.
Component Object Model
Component Object Model (COM) is a Microsoft software architecture and binary-interface standard that enables interprocess communication and reusable software components across different programming languages.
- 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-Presenter Target entity description: Model-View-Presenter is a software architectural pattern that separates an application into model, view, and presenter components to improve testability and maintainability, particularly in user interface code.
-
A.
Model-View-Controller
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.
-
B.
MVC
MVC refers to the Missouri Valley Conference, one of the oldest NCAA Division I athletic conferences in the United States.
-
C.
MVVM
MVVM (Model–View–ViewModel) is a software architectural pattern that separates an application's user interface from its business logic and data models to improve testability, maintainability, and modularity.
-
D.
Model Driven Architecture
Model Driven Architecture is a software design approach defined by the Object Management Group that focuses on creating platform-independent models which can be systematically transformed into platform-specific implementations.
-
E.
Component Object Model
Component Object Model (COM) is a Microsoft software architecture and binary-interface standard that enables interprocess communication and reusable software components across different programming languages.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
software architectural pattern
ⓘ
user interface architectural pattern ⓘ |
| abbreviation | MVP ⓘ |
| appliedIn | event-driven programming ⓘ |
| category |
architectural pattern
ⓘ
presentation layer pattern ⓘ |
| contrastsWith | Model-View-Controller in controller responsibilities ⓘ |
| decouples | view from model ⓘ |
| definesRoleOf |
Model
ⓘ
Presenter ⓘ View ⓘ |
| documentationLanguage | UML diagrams ⓘ |
| emphasizes |
passive view
ⓘ
supervising controller ⓘ |
| focusesOn |
keeping view as thin as possible
ⓘ
moving logic from view to presenter ⓘ |
| hasComponent |
Model
ⓘ
Presenter ⓘ View ⓘ |
| hasVariant |
Passive View
ⓘ
Supervising Controller ⓘ |
| influencedBy | Model-View-Controller ⓘ |
| ModelRole |
encapsulates application data
ⓘ
encapsulates business logic ⓘ |
| originatedIn | user interface design community ⓘ |
| PresenterRole |
acts as mediator between view and model
ⓘ
handles presentation logic ⓘ updates model based on user input ⓘ updates view based on model ⓘ |
| primaryGoal |
improved maintainability
ⓘ
improved modularity ⓘ improved testability ⓘ separation of concerns ⓘ |
| similarTo | Model-View-Controller ⓘ |
| supports |
mocking of views
ⓘ
test-driven development ⓘ unit testing of presentation logic ⓘ |
| typicalCommunication |
model not directly aware of view
ⓘ
presenter communicates with model ⓘ view communicates with presenter ⓘ |
| usedBy |
.NET developers
ⓘ
Android developers ⓘ Java developers ⓘ |
| usedIn |
desktop applications
ⓘ
graphical user interface applications ⓘ mobile applications ⓘ web applications ⓘ |
| ViewRole |
forwards user input to presenter
ⓘ
renders user interface ⓘ |
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-Presenter Description of subject: Model-View-Presenter is a software architectural pattern that separates an application into model, view, and presenter components to improve testability and maintainability, particularly in user interface code.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.