Triple

T9635014
Position Surface form Disambiguated ID Type / Status
Subject Single Responsibility Principle E232905 entity
Predicate clarifiedAs P80803 FINISHED
Object one reason to change, not one task to perform LITERAL FINISHED

How this triple was built (2 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: one reason to change, not one task to perform | Statement: [Single Responsibility Principle, clarifiedAs, one reason to change, not one task to perform]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: clarifiedAs
Context triple: [Single Responsibility Principle, clarifiedAs, one reason to change, not one task to perform]
  • A. clarifiesThat
    Indicates that one entity explains or makes another entity more understandable by removing ambiguity or confusion about it.
  • B. betterUnderstoodAs chosen
    Indicates that one concept, term, or representation is more accurately or clearly interpreted when viewed as another specified concept, term, or representation.
  • C. clarifiesStandard
    Indicates that one entity explains, specifies, or makes more precise the meaning or application of a given standard for another entity.
  • D. laterExplained
    Indicates that an earlier event, statement, or situation is clarified or made understandable by information provided at a subsequent time.
  • E. answeredBy
    Indicates that a question, request, or problem is responded to or resolved by a particular entity.
  • F. None of above.

Provenance (3 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.
PD Predicate disambiguation batch_69ccd5acfa5c8190aaba3cf548723604 completed April 1, 2026, 8:22 a.m.
Created at: March 30, 2026, 8:11 p.m.