Triple
T7794531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Thomas |
E180264
|
entity |
| Predicate | notableConcept |
P201
|
FINISHED |
| Object | DRY principle |
E97054
|
NE 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: DRY principle | Statement: [David Thomas, notableConcept, DRY principle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DRY principle Context triple: [David Thomas, notableConcept, DRY principle]
-
A.
DRY principle
chosen
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.
YAGNI principle
The YAGNI principle is a software development guideline that advises programmers to avoid implementing features until they are actually needed, helping reduce overengineering and unnecessary complexity.
-
C.
SOLID principles
SOLID principles are a set of five foundational object-oriented design guidelines that promote maintainable, flexible, and scalable software architectures.
-
D.
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.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca827d22208190b4dc5aa680edcf5d |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cae93b262c8190b55e5ab2bc72d894 |
completed | March 30, 2026, 9:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb13ea96cc819081ac26db3ecf4481 |
completed | March 31, 2026, 12:23 a.m. |
Created at: March 30, 2026, 4:31 p.m.