Triple
T7666562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Clean Coder |
E173637
|
entity |
| Predicate | relatedWork |
P37
|
FINISHED |
| Object | Clean Architecture |
E173638
|
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: Clean Architecture | Statement: [The Clean Coder, relatedWork, Clean Architecture]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Clean Architecture Context triple: [The Clean Coder, relatedWork, Clean Architecture]
-
A.
Clean Architecture
chosen
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.
-
B.
SOLID principles
SOLID principles are a set of five foundational object-oriented design guidelines that promote maintainable, flexible, and scalable software architectures.
-
C.
Clean Code: A Handbook of Agile Software Craftsmanship
Clean Code: A Handbook of Agile Software Craftsmanship is a highly influential software engineering book by Robert C. Martin that teaches principles and practices for writing readable, maintainable, and high-quality code.
-
D.
Design by Contract
Design by Contract is a software development methodology that treats software components as parties to a formal agreement, specifying precise obligations, benefits, and invariants to improve correctness and reliability.
-
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_69c699562484819086752091e3164a27 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c701c1383c8190ab5bf803bd6211a9 |
completed | March 27, 2026, 10:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c89b260000819088d744ea8dc53cd2 |
completed | March 29, 2026, 3:23 a.m. |
Created at: March 27, 2026, 4 p.m.