PUBLIC VIEWPOINTS

Frank Coyle

Source participant

1 sources · 4 viewpoints · 4 topics

Content updated:

Frank Coyle on agent validation workflow, neurosymbolic AI architecture, ontology-based business logic enforcement. Explore 4 viewpoints by topic, with evidence from 1 source.

Explore connections

Viewpoints by topic

Attributed viewpoints, ordered by source publication date. A snapshot of these conversations, not a definitive statement of someone’s beliefs.

Translations are for reading; original excerpts remain the evidence.

ontology design for AI agents

View this topic

Ontologies as formal shared conceptualizations

Frank Coyle defines an ontology as a formal specification of a shared conceptualization and says agents should be given that conceptualization of their domain.

Supporting evidence

Why Agentic Systems Need Ontologies — Frank Coyle, UC Berkeley

Original excerpt

It is a, a formal specification of a shared conceptualization, and that's what we wanna give to our agents. We wanna give them our concept-- our conceptualization of the universe, our universe, our domains.
Context

knowledge and, uh, graph technology really represents.

Start time comes from the supplied transcript. Playback alignment is awaiting review.

neurosymbolic AI architecture

View this topic

Neurosymbolic AI as LLM guardrails

Frank Coyle argues that neurosymbolic AI can help keep probabilistic LLMs on guardrails.

Supporting evidence

Why Agentic Systems Need Ontologies — Frank Coyle, UC Berkeley

Original excerpt

what I'd like to argue is that neurosymbolic AI sort of represents a way to keep the LLM on its guardrails, because LLMs are by nature probabilistic.
Context

And so

Start time comes from the supplied transcript. Playback alignment is awaiting review.

agent validation workflow

View this topic

Ontology-driven validation in agent loops

Frank Coyle proposes using ontologies after a tool runs, formatting the returned information for a validator that operates with domain ontologies.

Supporting evidence

Why Agentic Systems Need Ontologies — Frank Coyle, UC Berkeley

Original excerpt

if you look down there, a-after the, the tool is called, it said, "Tool runs," this is where ontologies could come in. The tool's gonna give us information. We put the information in a form that our, our, our, our validator can use.

Start time comes from the supplied transcript. Playback alignment is awaiting review.

ontology-based business logic enforcement

View this topic

Ontologies for catching domain-specific errors

Frank Coyle says ontologies could catch errors such as a second refund on one order or a payout sent to support instead of the buyer. He describes catching such errors in English as tricky.

Supporting evidence

Why Agentic Systems Need Ontologies — Frank Coyle, UC Berkeley

Original excerpt

A second refund on the same order is a, is, is a problem. [laughs] Ontologies could catch it, whereas it's ver- it's very tricky to do that in, in English. A payout sent to the support desk instead of the buyer, okay?

Start time comes from the supplied transcript. Playback alignment is awaiting review.

Statements by source date1

Statements are ordered by the original source publication date; differences in wording do not establish a change of position.