Triple
T2092660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agile Software Development, Principles, Patterns, and Practices |
E32704
|
entity |
| Predicate | explainsConcept |
P463
|
FINISHED |
| Object |
Single Responsibility Principle
The Single Responsibility Principle is a core object-oriented design guideline stating that a class or module should have only one reason to change, meaning it should be responsible for just a single, well-defined functionality.
|
E232905
|
NE FINISHED |
How this triple was built (4 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Single Responsibility Principle | Statement: [Agile Software Development, Principles, Patterns, and Practices, explainsConcept, Single Responsibility Principle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Single Responsibility Principle Context triple: [Agile Software Development, Principles, Patterns, and Practices, explainsConcept, Single Responsibility Principle]
-
A.
DRY principle
The DRY (Don't Repeat Yourself) principle is a software development guideline that emphasizes reducing repetition by centralizing logic and data to improve maintainability and reduce errors.
-
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.
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.
-
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.
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.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Single Responsibility Principle Triple: [Agile Software Development, Principles, Patterns, and Practices, explainsConcept, Single Responsibility Principle]
Generated description
The Single Responsibility Principle is a core object-oriented design guideline stating that a class or module should have only one reason to change, meaning it should be responsible for just a single, well-defined functionality.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Single Responsibility Principle Target entity description: The Single Responsibility Principle is a core object-oriented design guideline stating that a class or module should have only one reason to change, meaning it should be responsible for just a single, well-defined functionality.
-
A.
DRY principle
The DRY (Don't Repeat Yourself) principle is a software development guideline that emphasizes reducing repetition by centralizing logic and data to improve maintainability and reduce errors.
-
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.
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.
-
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.
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.
- F. None of above. chosen
Provenance (5 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba774ca881909f83cf65ffeb24bb |
completed | March 7, 2026, 5:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae2748f09c81908d471b02a185ec1e |
completed | March 9, 2026, 1:50 a.m. |
| NEDg | Description generation | batch_69ae27e4a6f88190a6af44f2cc822f31 |
completed | March 9, 2026, 1:52 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae2876710c81909451744f48337998 |
completed | March 9, 2026, 1:55 a.m. |
Created at: March 4, 2026, 7:43 p.m.