Triple

T9635000
Position Surface form Disambiguated ID Type / Status
Subject Single Responsibility Principle E232905 entity
Predicate relatedTo P37 FINISHED
Object Interface Segregation Principle
The Interface Segregation Principle is a SOLID object-oriented design guideline that advocates for creating small, specific interfaces so that clients only depend on methods they actually use.
E811519 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: Interface Segregation Principle | Statement: [Single Responsibility Principle, relatedTo, Interface Segregation Principle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Interface Segregation Principle
Context triple: [Single Responsibility Principle, relatedTo, Interface Segregation Principle]
  • A. Dependency Inversion Principle
    The Dependency Inversion Principle is an object-oriented design guideline that promotes decoupling by having high-level and low-level modules depend on shared abstractions rather than concrete implementations.
  • B. Liskov Substitution Principle
    The Liskov Substitution Principle is an object-oriented design rule stating that objects of a superclass should be replaceable with objects of a subclass without altering the correctness of a program.
  • C. 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.
  • D. Open-Closed Principle
    The Open-Closed Principle is a fundamental object-oriented design guideline stating that software entities should be open for extension but closed for modification, enabling systems to grow without altering existing, tested code.
  • E. SOLID principles
    SOLID principles are a set of five foundational object-oriented design guidelines that promote maintainable, flexible, and scalable software architectures.
  • 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: Interface Segregation Principle
Triple: [Single Responsibility Principle, relatedTo, Interface Segregation Principle]
Generated description
The Interface Segregation Principle is a SOLID object-oriented design guideline that advocates for creating small, specific interfaces so that clients only depend on methods they actually use.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Interface Segregation Principle
Target entity description: The Interface Segregation Principle is a SOLID object-oriented design guideline that advocates for creating small, specific interfaces so that clients only depend on methods they actually use.
  • A. Dependency Inversion Principle
    The Dependency Inversion Principle is an object-oriented design guideline that promotes decoupling by having high-level and low-level modules depend on shared abstractions rather than concrete implementations.
  • B. Liskov Substitution Principle
    The Liskov Substitution Principle is an object-oriented design rule stating that objects of a superclass should be replaceable with objects of a subclass without altering the correctness of a program.
  • C. 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.
  • D. Open-Closed Principle
    The Open-Closed Principle is a fundamental object-oriented design guideline stating that software entities should be open for extension but closed for modification, enabling systems to grow without altering existing, tested code.
  • E. SOLID principles
    SOLID principles are a set of five foundational object-oriented design guidelines that promote maintainable, flexible, and scalable software architectures.
  • 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_69ca848940cc8190b97cec654cb3bb4a completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9b2a0e2c8190ab5aaa223b1e1cde completed April 1, 2026, 10:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69d18237e2608190a3e7d45231a35efd completed April 4, 2026, 9:27 p.m.
NEDg Description generation batch_69d18333b5c4819090152a2da5e51e87 completed April 4, 2026, 9:31 p.m.
NED2 Entity disambiguation (via description) batch_69d183c8da2c8190a655c49994b94698 completed April 4, 2026, 9:34 p.m.
Created at: March 30, 2026, 8:11 p.m.