---
title: "Comment by Adam Lewis on \"Ontology-Based Context Engineering: When RAG Is Not Enough\" | Hashnode"
description: "Once the relationships between concepts are stated rather than inferred from embedding distance, the answer stops depending on the luck of the chunk. What I had"
url: "https://hashnode.com/posts/ontology-based-context-engineering-when-rag-is-not-enough/6aa3b54650f99ce700ab144b/comment/6ab19b74c676071a6bc94a96"
---

[Discussion](https://hashnode.com/posts/ontology-based-context-engineering-when-rag-is-not-enough/6aa3b54650f99ce700ab144b)

Comment [Ontology-Based Context Engineering: When RAG Is Not Enough](https://hashnode.com/posts/ontology-based-context-engineering-when-rag-is-not-enough/6aa3b54650f99ce700ab144b)

[Adam Lewis](https://hashnode.com/@nark3d)

[Sep 21](https://hashnode.com/posts/ontology-based-context-engineering-when-rag-is-not-enough/6aa3b54650f99ce700ab144b/comment/6ab19b74c676071a6bc94a96)

Once the relationships between concepts are stated rather than inferred from embedding distance, the answer stops depending on the luck of the chunk. What I had been underestimating was how much the phrasing around the question steers the answer. Looking forward to the rest of it.

[Elie Nehmé](https://hashnode.com/@elie29)

[Sep 25](https://hashnode.com/posts/ontology-based-context-engineering-when-rag-is-not-enough/6aa3b54650f99ce700ab144b/comment/6ab19b74c676071a6bc94a96#reply-6ab64fb82c44a281c0c99b5f)

Thank you for your feedback.

Exactly — that was one of the things that surprised me too. The question itself can steer retrieval more than we realize. Explicit relationships give the model a much more stable path. And I just realized I hadn't updated the article with the link to the second part — fixing that now. You can find more on my website: [https://elienehme.fr/en](https://elienehme.fr/en)

Thanks for reading!
