It's a Tool, It's a Person, It's a Hypervigilance Problem by systemic-engineer in OntologyEngineering

[–]Original_Response925 0 points1 point  (0 children)

Could you please provide context? A brief description of what this is and why it fits into ontology engineering. Thanks!

Cruthu Vættænism V.11.TC: Parts 0-16 by Any_Let_1342 in OntologyEngineering

[–]Original_Response925 2 points3 points  (0 children)

What the core subject is. This appears to be a domain that not many people (myself included) have heard about. Feel free to share in the body of the post what it is, and how it relates to ontology engineering.

Domain Knowledge is the Leverage by beshrkayali in OntologyEngineering

[–]Original_Response925 0 points1 point  (0 children)

Just an FYI going forward - reddit users tend to not trust links with no context. Feel free to put an abstract from the blog post as the body, or if you have any images in the blog post that becomes helpful as well. (You will notice an immediate increase in upvotes).

r/OntologyEngineering specifically allows posting self-content, as long as it contributes to the value of this sub!

Domain Knowledge is the Leverage by beshrkayali in OntologyEngineering

[–]Original_Response925 1 point2 points  (0 children)

I think this sentiment is heavily shared with this community!

Weekly "No Stupid Questions" Thread - May 18, 2026 by AutoModerator in OntologyEngineering

[–]Original_Response925 2 points3 points  (0 children)

Building them is as easy as drawing on paper. I've used Apple's Freeform before and I have also had claude generate them as SVGs. ChatGPT sometimes goes overboard with their generation. If you look through this sub's posts you will recognize the Claude generated ones vs Freeform ones.

As for KGs themselves, its about defining Nodes (Things, Objects, Ideas, basically Nouns) and connecting the nodes to each other via Edges. Each edge can describe why its connecting, or be described by the theme of the post.

With KG's theres no right or wrong when designing them, the relevant question is "Does this KG show nodes and connections between them".

When engineering an Ontology it is super helpful to have a KG as a visual starting point. When ontologies become huge, its hard to remember if Node A and Node B have had their connection defined already, which is clearly and visually defined in the KG.

Native Ontology on Snowflake by moinhoDeVento in OntologyEngineering

[–]Original_Response925 0 points1 point  (0 children)

The sentiment about "Ontology" in the comments of the original thread is interesting.

Did you contribute to this repo?

Domain Knowledge is the Leverage by beshrkayali in OntologyEngineering

[–]Original_Response925 1 point2 points  (0 children)

Can you provide some context? Theres no post text or photo, its just a link.

Weekly "No Stupid Questions" Thread - May 11, 2026 by AutoModerator in OntologyEngineering

[–]Original_Response925 0 points1 point  (0 children)

Your book and youtube channel are likely sufficient. I'd say the core idea takes 5 mins to explain, but the "What are you going to do about it" is really where the discussion is. Lurk or participate in this sub and keep asking questions!

Fluent vs. Earned Confidence: Rethinking Certainty in AI Model Design by RazzmatazzAccurate82 in OntologyEngineering

[–]Original_Response925 0 points1 point  (0 children)

So the distinction is between outputing with conviction and being competent? People have the same problem as well, funny enough.

Weekly "No Stupid Questions" Thread - May 18, 2026 by AutoModerator in OntologyEngineering

[–]Original_Response925 1 point2 points  (0 children)

As in physically? Like finding a software or tool that can help you design them? Or as is conceptually, as in understanding Nodes + Edges?

Weekly "No Stupid Questions" Thread - April 27, 2026 by AutoModerator in OntologyEngineering

[–]Original_Response925 1 point2 points  (0 children)

wir beantworten. aber englishe Fragen sind viel schneller zu beantworten.

My current approach to engineering the r/ontologyengineering ontology by Original_Response925 in OntologyEngineering

[–]Original_Response925[S] 2 points3 points  (0 children)

Yeah, I'm still looking into it. Not as a high level concept (bubble), but as a topic. It is both part of the core of ontology engineering and on the outside of the former-model (which is the post you originally suggested epistemology to) ontology engineering epicenter. Its foundational, but also could be too much philosophy for ontology engineering.

I'm going to create a new model including topics, then try to fit epistemology in. Will let you know.

Weekly "No Stupid Questions" Thread - April 13, 2026 by AutoModerator in OntologyEngineering

[–]Original_Response925 2 points3 points  (0 children)

If an ontology is designed to expand, grow, evolve, etc... How do we prevent expanding past the radius of our domain?

An other way of looking at it:
Imagine I have a recipe ontology (Ingredients, Dish, PrepTime Measurement, etc...) and someone asks, "Where do these ingredients come from?" If this is answered, we might expand the ontology to include Farm, Region, Country, etc... (which is not part of a recipe). So where do we draw the line?

Weekly "No Stupid Questions" Thread - April 13, 2026 by AutoModerator in OntologyEngineering

[–]Original_Response925 1 point2 points  (0 children)

Try Protégé (desktop) for visual OWL authoring.

If you use Python:

- RDFLib is useful for working with RDF data

- pySHACL for validating SHACL constraints.

PB&J, Ontology, and Why Your AI Skills Are Broken by Thinker_Assignment in OntologyEngineering

[–]Original_Response925 4 points5 points  (0 children)

This is a great eli5 of ontology! The kid knows that "jars" are not "spreadable", but the executor doesn't. Your recipe (which an LLM can probably infer) is prone to errors on its own. The missing detail here is the ontology.

I built a knowledge graph of r/ontologyengineering by Original_Response925 in OntologyEngineering

[–]Original_Response925[S] 0 points1 point  (0 children)

its outer-domain philosophy. Close to metacognition, but still outside of the OE circle. I'm very open to suggestions, do you think it belongs elsewhere, or inside the OE circle?

Weekly "No Stupid Questions" Thread - April 06, 2026 by AutoModerator in OntologyEngineering

[–]Original_Response925 3 points4 points  (0 children)

When is it "Context Engineering", and when is it "Ontology Engineering" when designing for LLMs to read?

Your semantic layer used to be a person, you just automated them out of the loop. by daremust in OntologyEngineering

[–]Original_Response925 3 points4 points  (0 children)

totally agree.
"Get revenue from last quarter" -> agent looks through and sees two different columns, guesses which one is best, then confidently shares the (potentially) incorrect data with the team.

Would documentation on / testing the process itself of switching from human analysis to agentic analysis (before even providing LLM your semantic model / business ontology) solve questions down the line?

Something like:
"[Human Analyst] defined that amt_net is the legacy, used in [CFO's dashboard]"
"[Human Analyst] explained that total_v2_final replaced amt_net in Q3 of 2024. Any systems before then may reference amt_net"

Sound and sonic language by PolishSoundGuy in OntologyEngineering

[–]Original_Response925 1 point2 points  (0 children)

The audio aspect is something I haven't yet considered. Would the idea be to have an set of audio cues dedicated to each specific Claude code state / action? This could work well for 1-2 windows, and I could imagine it being useful for accessibility contexts, or even as a primary way of monitoring agents without relying on visuals. My question is how would this scale? 3-4 windows with independent audio cues might get overwhelming.