Triple

T7540073
Position Surface form Disambiguated ID Type / Status
Subject Robert C. Martin E178251 entity
Predicate isKnownFor P22 FINISHED
Object SOLID principles
SOLID principles are a set of five foundational object-oriented design guidelines that promote maintainable, flexible, and scalable software architectures.
E672060 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: SOLID principles | Statement: [Robert C. Martin, isKnownFor, SOLID principles]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SOLID principles
Context triple: [Robert C. Martin, isKnownFor, SOLID principles]
  • 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. 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.
  • C. 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.
  • 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. KISS principle
    The KISS principle is a design and problem-solving guideline that advocates keeping systems and solutions as simple as possible to improve clarity, reliability, 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: SOLID principles
Triple: [Robert C. Martin, isKnownFor, SOLID principles]
Generated description
SOLID principles are a set of five foundational object-oriented design guidelines that promote maintainable, flexible, and scalable software architectures.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: SOLID principles
Target entity description: SOLID principles are a set of five foundational object-oriented design guidelines that promote maintainable, flexible, and scalable software architectures.
  • 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. 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.
  • C. 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.
  • 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. KISS principle
    The KISS principle is a design and problem-solving guideline that advocates keeping systems and solutions as simple as possible to improve clarity, reliability, 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_69c69f2be3888190a6667a27f8f195e9 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f873b17081908bb70aea0010d072 completed March 27, 2026, 9:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69c84f18e4dc81909ecd73b2b06b8d9c completed March 28, 2026, 9:58 p.m.
NEDg Description generation batch_69c853bc094c8190ba4e7ecb069c2c02 completed March 28, 2026, 10:18 p.m.
NED2 Entity disambiguation (via description) batch_69c85412e6308190893a500e2395bd94 completed March 28, 2026, 10:20 p.m.
Created at: March 27, 2026, 3:48 p.m.