923: Graph Algorithms, GraphRAG and Causal Graphs, with Graph Guru Amy Hodler

16 Sep 2025 · 1 h 4 min · 23 chapters

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

Graph data structures and graph algorithms, including graph fundamentals (nodes/edges, property graphs vs RDF triples), real-world applications (fraud/crime, recommendations, supply chain optimization), and emerging AI uses like GraphRAG, graph-based agent memory, multimodal graph modeling (images/audio), and causal graphs.

Guest backgrounds

Amy Hodler is a graph analytics expert; founder and executive director of GraphGeeks (graphgeeks.org) and co-author of an O’Reilly book “Graph Algorithms.” She previously worked at Hitachi’s IoT group, where unusual device behavior led her to complexity studies, network science, and graph modeling.

Key claims

Graphs capture relationships better than tables for dense, evolving interactions (“breadcrumbs” over time). Graph algorithms compute over network topology to reveal structure and behavior. Naive “ask everything” traversal (e.g., all-pairs shortest path) can be computationally expensive; constrain queries (e.g., top-K) and tailor data models. GraphRAG is hybrid: vector retrieval plus graph/topology reasoning to reduce RAG meaning gaps and support multi-step reasoning and dependency/sequence queries.

Notable examples

Crime/fraud rings and money laundering; Netflix-style director-based recommendations; supply chains (World War II troop supply routes, route planning, top-K optimized routes); PageRank (credibility; also telomere lifespan and contaminant toxicity); legal documentation dependency/ripple-effect analysis; multimodal graphs modeling images (ships’ relative motion) and audio (Doppler-based direction from police-car videos).

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Chapters

Tap a time to open that second in VO

Getting to Know Amy Hodler

0:45 to 1:40

Host Jon Krohn interviews Amy about her background and location.

“I am calling in from Little Kettle Falls, Washington.”

Understanding Graphs

1:40 to 3:20

Amy explains the basic concepts of graphs and their terminology.

“is not to discuss the great outdoors, as wonderful as it is, but to talk about graphs, which you are such a deep expert in.”

Properties and Types of Graphs

3:20 to 5:00

Discussion on property graphs, RDF, and their applications.

“So you can have your nodes and your relationships can have multiple properties.”

Importance of Properties in Graphs

5:00 to 6:40

Amy discusses the role of properties in graphs and their flexibility.

“I would say with RDF, there's a lot more enforcement of rules and logic.”

Amy's Journey into Graphs

6:40 to 8:20

Amy shares her unexpected journey into the world of graphs.

“It can be zero to one if you need to normalize something and you need to develop a strength on, especially on the relationships.”

Real World Applications of Graphs

8:20 to 10:10

Exploring how graphs are used in crime analysis and monitoring behavior.

“You can network, look at any of those as network.”

Further Use Cases for Graphs

10:10 to 12:10

Amy discusses recommendations and supply chain optimization using graphs.

“You actually, before we started recording, you were telling me about how with crime, that is often a really good use case of graphs.”

Understanding Supply Chain Graphs

14:00 to 15:29

Learn how graphs optimize supply chain routes and decision-making.

“And so you need to be able to understand the patterns and understand how things shifting in the supply chain may shift your predictions.”

Graph Traversal and Complexity

16:04 to 23:34

Explore the complexities of graph traversal and its computational challenges.

“I'm starting to see that, how there are graphs everywhere and how you are seeing them out on your hikes.”

Graph Algorithms in Practice

23:34 to 28:00

Dive into various graph algorithms and their applications in real-world scenarios.

“And so, yeah, so is there anything else that you want to add in around graph algorithms or your graph algorithms or Riley book before I move on to the next topic?”
Show all 23 chapters

Understanding Graph Applications in Biology

28:00 to 29:10

Explore how graph theory applies in biology and complex systems.

“And the tricky thing is that telomeres extending is also one of the key causes of a metastatic cancer tumor.”

Resources and Trends in Graph Research

29:10 to 31:08

Discover where resources are allocated in graph research and the focus on fraud detection.

“You mentioned there that biology maybe isn't the place that a lot of resources are going for graph research.”

Legal Documentation and Graph Analysis

31:08 to 32:52

Learn about the potential of graph theory in analyzing legal documentation.

“And so looking at legal documentation and helping your lawyers and your business analysts understand it better is easy, low-hanging fruit.”

Introducing GraphRAG: A New Paradigm

32:52 to 35:36

Unpack the concept of GraphRAG and how it enhances traditional models.

“So those kinds of use cases that you were just describing there, like the legal document search, is that GraphRag?”

The Intersection of Graphs and RAG

35:36 to 37:18

Discuss the complementary role of graphs in enhancing retrieval augmented generation.

“So there are a number of reasons why RAG has, some people feel like we're past the RAG moment.”

Getting Started with Graphs and Tools

37:18 to 41:39

Find out how to get started with graphs, recommended tools, and conferences.

“that has topological significance that you're just not getting.”

Discussion on ODSC Conference

42:00 to 43:26

Learn about the importance of the ODSC conference in the graph community.

“And I'm not just saying that because they sponsor the show.”

Introduction to Graph Geeks

43:26 to 48:26

Discover the story behind the creation of Graph Geeks and its community.

“And he actually, he now spends other than, so he professionally hosts the Modern CTO Podcast.”

The Future of Graphs

48:26 to 53:56

Explore upcoming trends in graph technology including multimodal and causal graphs.

“It sounds like you're doing an amazing thing for the graph community.”

Book Recommendation on LLMs

53:56 to 56:00

Amy recommends a thought-provoking book on large language models.

“The final thing as far as emerging, if we want to add this at some point, is causal graphs.”

The Value of Understanding LLMs

56:00 to 58:08

Learn about the importance of diving deeper into large language models and the benefits of diverse perspectives.

“Do they have the appearance of thinking?”

Book Club Insights

58:08 to 58:31

Discover the advantages of participating in a book club focused on data and AI topics.

“I also fantasize about being under the leaves of a book.”

Episode Highlights with Amy Hodler

58:31 to 59:23

Recap of key insights shared by Amy Hodler on graph algorithms and their applications.

“So yeah, as I already said a few minutes ago, this has been an amazing episode.”
Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:00Jon Krohn:Welcome back to the Super Data Science Podcast. I'm your host, Jon Krohn. Today, we've got an episode for you all about graphs. No, not plots, but the powerful graph data structure with many time graph analytics book author and in general, the world class graph analytics guru, Amy Hodler. In today's episode, Amy introduces the graph data structure, graph algorithms, and all kind of cool new graph applications, including GraphRag, graphs for LLM memory and causal graphs. Amy is absolutely terrific at explaining these concepts in an easy-to-understand way, so enjoy this one. This episode of Super Data Science is made possible by Dell, Intel, and the Open Data Science Conference.

0:43Jon Krohn:Amy, welcome to the Super Data Science Podcast. Where are you calling in from today? Well, thank you for having me. I am calling in from Little Kettle Falls, Washington. Little Kettle Falls. What's it like at Little Kettle Falls, and is there a big one nearby? There is not. There are under 1700 people in this small rural area of Northeast Washington. So a lovely, beautiful area, but definitely small town. Nice. Lots of outdoors, I guess. Absolutely. We hike every day. Lovely. That sounds nice. Living in Manhattan, it is something I literally yearn for. I sometimes lay in bed just in the middle of the day and imagine that I'm under a canopy of leaves.

1:28Jon Krohn:There's something soothing about that. Oh, well, come on out. We'll do some kayaking, some biking and hiking. Oh my goodness, that sounds so great. Now, the real purpose of you being on the show is not to discuss the great outdoors, as wonderful as it is, but to talk about graphs, which you are such a deep expert in. And so first off, I guess we should kind of explain what graphs are quickly off the bat, just to make sure people aren't thinking about plots. Yeah, absolutely. That's usually one of the first questions are, what are graphs? So graph is actually a term that comes from mathematical history going back to the 1700s, actually.

2:08So graphs have been around for quite a long time. And it's basically a way to capture relationships in data. And so if you think about when you go to a whiteboard and somebody asks you to draw out your process or your organization and you do circles for the nouns and you do lines between them and those are usually the verbs those are the relationships that is all a graph is it's just a way to capture entities think of them as nouns and relationships think of those as verbs so that's

2:42Jon Krohn:simply what a graph is very nice and for our data scientists out there our statisticians out there the dots in the graph are nodes, right? And then the connections are edges. Are there any other key terms that we kind of need to know in graph world? I would say nodes are also called vertices or vertex, if you will. And your relationships can be edges or links. So there's a lot of different terminology, but the feeling is all the same. Sometimes people do talk about property graphs, which are for your data scientists out there, are graphs that have properties on them. So you can have your nodes and your relationships can have multiple properties.

3:27And it has a kind of a very hierarchical feel to it, at least to me. And then people sometimes will talk about RDF, or resource description framework, or triples. And those are a little more verbose way of talking about nouns, verbs, and objects. So subject, object, predicate is what you'll usually hear about. Those are just different ways to model those relationships. So those are the other terms that you hear most. Network science, of course.

3:56Jon Krohn:That's cool. Tell me about those things. Tell me about RDF in a bit more detail. You talked about object, predicate. Maybe you could give me an example so I can wrap my head around that. So it's just a different way to think about So it's another way to generate a sentence, if you will, or a fact. And so you might have something where Amy works at company, and you can basically create that with a triple. So you have Amy, and then the concept of works at, and then you have the company or whatever the company name is. And so that's just a, that's the original way that, that a lot of graphs, knowledge graphs came about.

4:40It has to do with the semantic web. So it's been around for a long time. And there's a lot of academic research around that tends to be more verbose than your property graph. And so depending on different people needs. So depending on your need, you might go with something that is based on a resource description framework or RDF, or you might go with something that's a property graph, which has a little more flexibility. I would say with RDF, there's a lot more enforcement of rules and logic. And with a property graph, there's a lot more flexibility. So depending on the team's need, you might go with something that's highly flexible, but has less enforcement of logic and rules, which can be good, but it can also get your team in trouble.

5:29Or maybe you need that sort of flexibility. So it really just depends on team needs.

5:35Jon Krohn:Right. And so something in the little bit of graph theory that I know, is it right to say that one of those properties can be like a quantity? So you could, for example, you could imagine your social media network where everybody that you're connected to on LinkedIn, you're connected to them by an edge. And so everyone, including yourself, is a node. You have these edges connecting you. And then you could say have, you know, you could have a quantity. I don't know if this is the same as a property. but you could have a quantity on each of those edges, which is how many times you viewed their page or how many times you've commented on a post of theirs or something like that.

6:15Yeah. So the properties can be just about anything. So that's the, at least in a property graphs, and that's part of that flexibility. So it could be anything from a descriptor, like a color of a car, to the make and model, to the year, to a quantity. It can be a strength. So it can be, and in fact, that's one of the ways people get around some of the explosion of data is to just do a aggregation of the number of times you've looked at something. So you can basically create a strength. It can be zero to one if you need to normalize something and you need to develop a strength on, especially on the relationships.

6:56A lot of times you'll see that strength, but it can also be a geospatial. So you can put a geospatial code in there. It can be a lat long if you are doing geospatial. It can be a string, a number, various different data types as well, and even sometimes a list, depending on what graph you're using. So you can use it to then refer to other things. So yeah, lots of flexibility in what the properties can be.

7:22Jon Krohn:How did you get so into graphs, Amy? I mean, you're the founder and executive director of a company called GraphGeeks, which specializes in bringing together people that relish connected data. So I guess people who love network science, as you referred to it earlier in the episode. How did you get so into graphs? That's an interesting story. So by accident, what's the story? The way you fall in love with anything is while you're doing something else. So I was actually working at Hitachi with the IoT group. And what we were noticing was that the end devices had unusual behavior. So I would say I thought it was emergent behavior.

8:06It wasn't. But it was this behavior of end devices when they started to interact with each other. That led me to complexity studies and network science because that studies how things interact together, whether you're talking about brain banks, IoT devices, or cars on a freeway. You can network, look at any of those as network. And so starting to try to understand why these edge devices were having unusual behavior when they worked together led me to start looking at network and network science. And then how you deal with a lot of network science concepts is using a graph. Because until you can represent your network as a graph, you then can't use, You that's when you get to use computer science capabilities because you have to model it in a way that computers can deal with it.

9:03So that led me to taking classes in graphs just to understand them. I had a good friend that was working at Cray at the time, the old supercomputer company, Cray. And they had a graph engine and he picked up the phone one day and said, hey, I think you might be you might be interested in this graph stuff. what's that about tell me about it uh and i just never look back because and i will say once anybody who's interested in graphs and network science once you start seeing the world um as a complex relationships between things you can't unsee it it's just it just it's so obviously the foundation of most of what the world is yeah so when you're hiking around

9:49Jon Krohn:in Washington state, you're supposed to be relaxing, but you're really just kind of making graphs in your mind. And you're saying that's not relaxing? Yes. I think about graphs and networks all the time because how do you not think about relationships between things? Cool. All right. So let's talk about some real world use cases. You actually, before we started recording, you were telling me about how with crime, that is often a really good use case of graphs. It can give you insights that you couldn't get with any other kind of approach. Yeah. And I would say finding bad behavior, whether we're talking about money laundering, that's a really typical one, fraud, fraud rings, but also international criminal organizations as well.

10:40Even things like supply chain crime as well, which is actually quite significant. The reason why graphs are so good about finding aberrant or bad behavior is that if you think about how somebody trying to hide their tracks, they don't, if you have activity going on, usually there's multiple touch points in criminal behavior. So it's not like somebody walks through the door and advertises that they are doing something criminally bad. They're actually trying to act and behave in a way that is, air quotes, normal to other customers or patients or what have you. And what you really need to do is be able to understand, connect the dots between multiple behavior and touch points over time.

11:31And which is, if you imagine what that would look like, that looks like breadcrumbs. And you're having, you can almost, I can see the graph in my head. You have these dots of touch points and links between them, relationships, and you breadcrumb through that to see aberrant behavior or an aberrant or an anti-pattern or pattern that shouldn't be there. And then the other thing is those things usually happen over time. So you can't just snapshot in and look for a bad actor. You have to be able to look at that over time and look at how the behavior develops over time. And the other thing is really bad behavior is rarely a one person or one entity point in time thing.

12:12It usually has multiple different collaborators. And so again, you need to be able to see the relationships between those collaborators and their behavior and their addresses and, and, and. And so you can imagine that gets into lots of dots and links between them. And that's hard to look at as rows and tables. If you look at that as rows and tables, you're just not going to see a pattern. And graphs have that unique ability to pull that important pattern out so that we can see that.

12:42Jon Krohn:You explained that really well. That was really easy to understand and gripping, frankly. What other kinds of use cases are out there in addition to crime? Well, so recommendations is a classic one as well. So for example, like for Netflix, if they're recommending a movie to me that I haven't seen, but it's a movie that has a director in it that I like or a director in it that I maybe like, but the other people who like that director recommend this other movie. And so you can build a similarity based on behavior and what people like and don't like. So that's classic recommendations. You see that all over the place.

13:26The other thing you can do, you can do things like optimizing networks of things like supply chain. We all saw supply chains break down during COVID, totally broke down. And part of that was because most of the way we were looking at supply chains was looking at the past. And this is a classic machine learning mistake, is that you do correlations, you make predictions based on what you've seen in the past. But if you don't understand your network, your customers, your supply chains, your partners very well, and you're just predicting based on what you've seen in the past, when there is an event that shifts the underlying reality, you are going to fall down, you're going to make wrong predictions.

14:05And so you need to be able to understand the patterns and understand how things shifting in the supply chain may shift your predictions. And you can do things like finding the optimal route. So graphs historically, and I think World War II, they started being used for supply chain, looking at supply chain during, actually troop supply chains during World War II. And if you have something that blows up, or you have a railroad that can no longer be used, you need to look at another route. And so graphs are really common for route planning, Uber uses graphs, you know, things like that. Like how do you find the best route?

14:46It's all through different points. But if you, in a supply chain standpoint, if you have a warehouse that goes out of commission or a port that you can no longer dock in, what's your next best route? And that is a common graph used in supply chains is the top K or the next, you know, the top routes that are optimized for these complex shipping and delivery routes. So that's another really common one would be supply chain. But quite frankly, anytime you have connected data, you can use graphs to help you optimize.

15:21Jon Krohn:Data scientists, it's time to talk about your tech. With Windows 10 support coming to an end, now is the perfect moment to rethink your setup. Enter Dell AI PCs powered by Intel Core Ultra processors. These devices are built for the demands of modern data science, delivering faster performance, smoother multitasking, and the power to handle even the most complex workflows. Whether you're training machine learning models or analyzing massive data sets, these PCs are designed to keep you ahead of the curve. Don't let outdated tech slow you down. Visit dell.com slash shoppcs to explore how you can upgrade your device and elevate your work.

15:58Jon Krohn:That's dell.com slash s-h-o-p-p-c-s. I'm starting to see that, how there are graphs everywhere and how you are seeing them out on your hikes. Crime and supply chain, all kinds of real world use cases. You hear, sometimes I hear, maybe you don't hear, sometimes I hear complaints that things like graph traversal, so doing operations over graphs are tricky, can be computationally expensive, maybe relative to some other kinds of approaches. What do you say to that? And maybe this is also the time to bring up that you wrote a great or co-authored a great O 'Reilly book called Graph Algorithms. Is that about kind of graph traversal and making the most out of this data structure or is it something else?

16:46It is. That book, the Graph Algorithms book that I co-authored for O 'Reilly and Graph Algorithms in general, it's focused on, I would say, the overall algorithms that are usually a little more holistic graph analysis. So trying to understand your graph and pull out important information. Graph traversal has two elements. You do see graph traversal in graph algorithms, but you also see graph traversal in ad hoc queries. And I will say in ad hoc queries, they can be tricky because you don't know how somebody is going to ask the question. And that can be very tricky because if you imagine a pair-wise question, the classic joke is, amongst graph people, one of the classic jokes is you wouldn't believe, again, I had somebody ask if we could calculate the shortest path between all pairs.

17:46All pairs shortest path is a classic algorithm. And the key word there is all. And if you imagine looking for the route between every two pairs of nodes in your network and comparing all of them and looking for the shortest, that is computationally crazy. You wouldn't do it. There's a ton of tricks to get around that. But I think graphs can be computationally complex. And if you approach it with a very naive sense of, I'm just going to ask everything I can ask, I'm going to ask for all peer shortest path, you will have problems. So you have to have, I guess, just some thought. It's very flexible.

18:27You can do just about anything. And therefore, you're empowered to do things you shouldn't do. So it's just coming with a little bit of thoughtfulness on do you really need all pairs? No, you probably don't. You probably are looking for all pairs among the top K. That's an easy way to get over some of that computational complexity. The other thing is with the ad hoc queries, if you can figure out what are most common queries that are needed with your organization, you can then tailor those and optimize those to both your real needs, but also you can tailor your data model. So your data model can impact your query timeframes as well.

19:08So graphs, they're a different model. They're a very powerful model, but it does make sense to have a little more thoughtfulness when you're approaching whatever the business problem might be. Cool.

19:23Jon Krohn:So I got an insight there perhaps into another way that data can be stored in a graph format. Just by you saying the question, shortest distance, it implies that there's not an arbitrary distance or that they're kind of equidistant. It sounds like you could kind of have a location in a two-dimensional or three-dimensional or many-dimensional space for each of the nodes. Is that right? Yeah, you can look at graphs as a dimensional space. It's funny, when I talk about how far away things are, I think of the number of hops. I see. But there's also a distance, if you imagine a relationship you talked earlier about, or you asked earlier about having numerical values on relationships, you can easily do that as well.

20:15And so you might actually have a numerical distance on your relationship that is actually related to a physical distance, or often it can be related to a time, cost in the supply chain, like how much does it cost to go between this port and that port? Those can all be considered distances. But yeah, when I'm thinking about computational overhead, I'm thinking about number of hops. And hops, so you hop from one node to another, from one person to another, Like, you know, John, you and I were introduced by, reintroduced by somebody else. We would have been, you know, a hop out. So we weren't a direct connection, but we had a hop to go through.

20:55And so you have to hop between those. And that can be, that's where the computational complexity can come in. Those hops are often, in a relational world, are often joins. And so if you have a lot of hops, in a relational world, you have a lot of joins. And that can also be computationally complex.

21:13Jon Krohn:Right. Shout out to our mutual node, Michelle Yee, who was in episode 915. Absolutely extraordinary individual she was. It's a great episode for people to listen to. Yeah, she's like you, outstanding at explaining concepts and funny and warm. Both of you share a lot of those attributes. We could list those as, what is it again when you have, when a node can have Properties. Properties, yes. Okay, funny story about Michelle. Michelle and I love to present together, especially in person. We started off, when we got to know each other, I realized she has a very sarcastic sense of humor. And so we started presenting together with the goal of trying to make each other laugh.

22:08And so when we do present, if you do have a chance to see Michelle and I together in person, And we try to hide last minute photos or jokes for each other to make the other one laugh live and unexpectedly.

22:21Jon Krohn:That's funny. Yeah, she got some good giggles out of me while we were recording for sure. And it's also it's amazing given that. I mean, I guess she has been now in the United States for a long time, but something like, you know, sarcasm. I think of it as kind of one of the higher levels of comedy. I don't know if that shows my, maybe I'm not that sophisticated of a person, but I, you know, sarcasm, I think, you know, it shows, you have to have a pretty deep understanding of a concept to know that this is something that people, people are expecting one thing. This is what usually happens when you use these kinds of words, when you set up this kind of scenario.

22:58Jon Krohn:And so therefore people should be able to infer, even if I'm dryly saying something that I'm making a joke. And so, yeah, it's, it's, you know, she, she lived in Korea until she was a teenager. And so to have that command, but it sounds like she gets a pretty high command of, she speaks, I think half a dozen different languages and. A crazy number. I, uh, yeah. Astounding, uh, you know, to, to me that you can have that kind of command and, uh, yeah, not have it be native, but that's, that's a very, yeah. Anyway, people can, people can listen to episode nine 15 for more on Michelle. We will return to our regular programming now with graphs.

23:37Jon Krohn:And so, yeah, so is there anything else that you want to add in around graph algorithms or your graph algorithms or Riley book before I move on to the next topic? Yeah, I would say graph algorithms. One of the reasons why I was smitten, and graph algorithms are my favorite part of graphs in general, is that if you imagine that either supply chain or fraud or crime or social network hairball that when you have a lot of nodes in connections, you can have a very dense, complicated to air quotes look at. And it's hard to see if you look at tables row, if you look at an average, you're not getting the structure of a network.

24:20The topology of a network is really indicative of the behavior within a network, like whether your network is growing, whether it's breaking apart, whether it's dying, whether it's clumping together, those are often driven by internal dynamics of your network science. And you can't very easily see those with statistical methods or with machine learning methods. But graph algorithms compute over topology. They compute over structure. And so the results of them will actually tell you something that you didn't know about your network and you can infer meaning from that. And that to me is so important right now because a lot of times I feel like in this moment, this machine learning, Gen AI moment, we are predicting the next item in a sequence, but we're not understanding our network, our customers, our patients, our supply chain as well.

25:17And so understanding some, inferring things about the network itself can be really helpful. A classic algorithm, graph algorithm, everybody knows is PageRank. So that was invented by Larry Page. We've all seen it when we Google. And we know that that infers credibility of a source. That was the original intent. Now you can use PageRank. You see PageRank used for things like inferring lifespan of a telomere in a brain, you see, which is a really cool use case. You see it for looking at toxicity of, um, of contaminants. It can be used so, so many different ways. Um, but it's the reason is because it understands the topology of the network.

26:02And then it tells you something like, what is the important node in a network? Same with community detection and, you know, so many other graph algorithms.

Read the full transcript

26:11Jon Krohn:Wow. Those were a lot of great examples that you were able to just enumerate there. I love that the telomere one is particularly interesting to me. I have a PhD in neuroscience. Oh, fascinating. Yeah. And so these kinds of things around. So some listeners may be aware that your lifespan as an organism is basically dictated by how long your telomeres are, which are things that are made by, I think basically always your mom and your dad when they produced the the sperm and or the egg that led to that led to creating you the the telomeres were extended um basically the it's it adds kind of garbage dna or dna that doesn't have any genes in it on the ends of your dna so that over your lifespan every time your cells um replicate so you go you You go from a sperm and an egg to a single cell, and then two, and then four, and then eight, and 16.

27:15Jon Krohn:And every time that happens, your DNA has to be copied. And then throughout your lifespan, as your cells continue to divide, your telomeres shrink, shrink, shrink, because the mechanism that copies your DNA needs something to clamp onto, and so it clamps on right at the end. And so those telomeres that were added on by your parents, thank them for that, is gradually eaten into over the course of your lifespan. And so a lot of what we consider to be aging is your telomeres being shortened. And your telomeres run out in some of the tissues in your body, and you're starting to eat into real meaningful genes.

27:58Jon Krohn:And so people who want to solve aging, a lot of it is about figuring out how you can have your telomeres grow while you're still alive without needing to create a sperm or an egg to be able to have those telomeres extend. And the tricky thing is that telomeres extending is also one of the key causes of a metastatic cancer tumor. Yeah, it's definitely a balance. Yeah. I mean, and the graphy element of that is just understanding the connections between things. And biology and biologists are very open to and understand a graphy way of looking at things. So there's a lot of use cases in biology as well.

28:44probably not where the biggest funding is in graphs, but, but there's just a natural understanding when you, when you talk to people with any kind of a healthcare or life sciences background that they just kind of, they get the fact that things are connected and the, the, you can use graphs to understand the flow of resources, which you can model sugar, you know, the flow of sugar through the body in that way. So there's, you know, if any, Anytime you're looking at highly complex systems, yeah, you end up getting into graphy theory behind that.

29:16Jon Krohn:You mentioned there that biology maybe isn't the place that a lot of resources are going for graph research. Where do you see a lot of resources going? If our listeners are thinking, wow, graph sounds super interesting, or I already am a graph expert, I'd love to find lots of fertile ground, where do you think they could find it? It's changed over time. So I would say, I hate to say fraud, fraud, and fraud, but finding bad actors. And when I say resources, I'm thinking commercial funding. And if you were doing a startup, what area would you focus in? So fraud is always, I want to say evergreen, but it is crowded.

29:55So you have to have a different way of looking at it or some kind of unique quality of how you're looking at it. So, you know, always throw fraud in the mix, whatever you're doing, just throw it in there and it's a door opener and people understand it. As cybersecurity is hot, again, it's starting to be a little crowded, but it's hot for graphs because, again, talking about how people try to hide and just the increase, the exponential increase in cybercrime right now means that people are looking at all different ways of tackling it. And so I think graphs and cybersecurity make a lot of sense, and in particular, when combined with other technologies as well.

30:39So it's another view on what you might already be doing. There's also some emerging use cases that I don't know if I would say reemerging that people had talked about previously, but are now becoming more tractable because they're combining it with LLMs and Gen AI. one of the ones that I would say are fairly low hanging fruit and probably people could build, I don't want to say build on their own, but for lack of a better word, you could probably build your own is documentation analysis. So if you think about like legal documentation, this is one area that I'm surprised not everybody's doing because it doesn't seem like that heavy of a lift, But legal documentation tends to have a lot of links to other caveats, other laws, sub clauses, sub clauses of sub clauses.

31:32And if you change this, what's the ripple effect of the connections to something else that might, you know, you might actually be signing something that is impossible to fulfill because of the rippling connections and requirements. And so looking at legal documentation and helping your lawyers and your business analysts understand it better is easy, low-hanging fruit. It's easier now because you can use the LLMs, the parse, the language, and then use the graph to understand the connections between the different documents. Just for basic document review and understanding, we even see this in help desks.

32:10So helpdesk looking at their own documentation, their own complicated documentation. And I talked to somebody just in April that was trying to figure out their massive reams of documentation and help their support line get through their own documentation because there was just so many different connections and links and threads. Anytime you want to pull a thread, but also lawyers as well are looking at it. So those are some of the interesting use cases that aren't necessarily new, but because of Gen AI coming in and large language models coming in, the combination are allowing these old new use cases to become just easier to accomplish.

32:53Jon Krohn:So those kinds of use cases that you were just describing there, like the legal document search, is that GraphRag? It can be. It can either be straight graph or you can use GraphRag. I would say right now, everybody's excited about GraphRag. So I would expect that to be somewhere in the mix, but it doesn't have to be, and it wasn't always. So Caterpillar uses Graphs and has for years for some of their support documentation and support staff. And that was before any of us had talked about RAC. But I would imagine, I don't know, haven't talked to them lately, but I would imagine And now they've got RAG in the mix and they're probably have a chat bot that, you know, is talking to that documentation as well.

33:35Jon Krohn:That's right. So let's talk about that in more detail, I suppose, if this is such an exciting area, GraphRAG. So retrieval augmented generation RAG, probably a lot of our listeners out there are already familiar with the term, but it's this idea of being able to search over. Well, so you start off by having, say, a large number of legal documents or Caterpillar's uh in caterpillar that's like the it's not a tractor company what do you call those i would call it heavy heavy equipment because they do a lot they do a lot of different equipment yeah if like like a lot of equipment with tracks on them it's the caterpillar right uh yes yes yes lots of lots of legs lots of uh points on the ground i suppose yeah um so yeah so whatever these use cases, you have lots of documents.

34:24Jon Krohn:You start by converting all of those documents into a vector representation, meaning a location in some high dimensional space. So you can visually think about it like in a two dimensional space or a three dimensional space, but in practice, it might have hundreds or even thousands of dimensions and the documents end up closer together because they're more, the meaning in the documents is more similar. And so LLMs have been great at figuring out that similarity and being able to get related documents close to each other. And so once you have all those documents close to each other, you can use reg, retrieval augmented generation, to say have a user ask a question.

35:05Jon Krohn:And that question is then in real time very quickly turned into that same kind of vector representation, the same kind of location in a high dimensional space. You can find related documents, you can pull them back, And then you can use an LLM to search over that relatively small number of documents you pull back to generate some response to the user's query. So, I mean, you can correct or change anything that I just said about RAG. But I'd love to hear now how we can take that RAG idea and how it becomes graph RAG. Yeah. Yeah. So there are a number of reasons why RAG has, some people feel like we're past the RAG moment.

35:51It's just things get hot, people get disappointed, and then they want to improve it. But there are several reasons why RAG has plateaued, I would say, a little bit in its performance. And that's why people are bringing in Graph as well to help out with it. It doesn't replace. It augments. Augments? RAG? Anyhow, I don't know what the acronym of GRAG or who knows what it might be. But you've seen problems with RAG basically with things like getting a plateau when your answers and your questions, your questions and answers don't align very well, especially semantically. And so you have this kind of meaning gap.

36:40So semantic just means meaning. But you have this meaning gap between what somebody's asking and the question, and the context isn't really well understood. So you see things like that. You see things like the ability to diversify the data you're pulling from. So RAG does really well with trying to extend what your retrieval is already doing. And so the retrieval effectiveness, you know, pure semantic vector search can be insufficient. So you might get an approximate match rather than an exact match, or you might want a match that has topological significance that you're just not getting. You might also need to do multi-step reasoning.

37:27So if you think about agentic rag where you need larger context windows, or you need to pull in diverse data sets, or you need to look at the previous responses to come up with a better response, graph can help with that in general, because again, we're looking at relationships, and that gives us context, and we're able to pull in topology as well. And so I think of graph and And graph rag gives us, vector search gives us really good summarization. It gives us really good fuzzy matches. If you're doing a full text search, you can get some exact matches. But graph gives us structure as well. Again, it's that topology.

38:18And that gives us matches and answers of things like dependencies, serial, things that might have serial dependencies or you might have to do them in a sequence. It's also good at aggregations, you know, especially if you're doing aggregations over multiple data sources and things like that. So I always think of, I think of graph in the graph rag as rag and. It's like you, you know, just, you don't want to just have one type of, you know, augmented generation. You want to include those other capabilities. Graph lets us do that. And it also helps us stitch things together because of the connections it has as well.

38:59Jon Krohn:So am I correct in understanding that they kind of happen in parallel, that you would be doing like a vector search as well as a graph search in parallel, and so then you get the best of both worlds, you get the fuzziness of the vector search with the specificity of a graph search? Yes, actually, when you think about vector and graph in graph reg, or it really should be called hybrid rag. That is the very thing you do see. And the results that I've seen, and this is an evolving space. So ask me in six months, question might be different or the answer might be different. But what I've seen is this hybrid in parallel that seems to get the best results.

39:39And then you have a method to then blend the results at the end and then augment that in an ongoing fashion.

39:48Jon Krohn:Very cool. So I'm sure a lot of our listeners out there are saying very cool with me right now. And so all of our hands-on practitioner listeners, whether they're data scientists or software developers or AI engineers, they might be wondering how they should be getting started with graphs. It could be GraphRag or just getting going on graphs in general. What are the key tools out there? Or I guess, what are the ones that you recommend people get started with? Yeah, I always think about thinking about your use case in mind. I mean, graphs are just fun in and of themselves. There's a lot of material.

40:23If you Google graph theory, there's a lot of fun material. But I would think about your use case and applying it in that manner. I try not to recommend specific tools, but there are a couple vendors that have really nice one-on-one material that you can use to get up to speed. I would say right now, don't lock yourself into one methodology. In the past, several years ago, like maybe three, four years ago, it was assumed if you were going to add graph to your capabilities, you had to have a graph database. That is no longer the case. There are several vendors out there that allow you to project a graph with a computational graph, so a classic graph engine or a graph layer.

41:09There are several vendors that also allow you to poke into your table data and ask a graphic question of your table data and just use that projection to answer the question and then drop it. And so depending on your need, there's a lot of different options for you. And there's no one option that's good for every situation. So looking at your own tech stack is probably real important. There's a couple conferences I really like. If anybody, to give a shout out to the Open Data Science Conference group, they do conferences in the East Coast, West Coast, Europe. They also do virtual conferences or virtual training as well.

41:57I like that because you get a broader spectrum of opinions and different ways of looking at graph, but also how it fits into the bigger picture as well.

42:08Jon Krohn:ODSC is my favorite conference as well. And I'm not just saying that because they sponsor the show. And they literally, they actually, in your episode, Amy, you can possibly know this because you don't know what ads we're going to put in. But at the, around the 30 minute mark in this very episode, there's an ODSC West 2025, uh, sponsor message. Uh, I absolutely love, uh, ODSC. I think it's the best for hands-on practitioners. Uh, because I'm in New York, I have the privilege of, uh, speaking at East in Boston in the spring most years. Um, and I get out to West, uh, or it's pretty much always on Halloween.

42:51Jon Krohn:uh i i get out there whenever i can sometimes my travel schedule doesn't permit it but if it does i'm always at west as well i love it michelle and i will be there this year i'll have to try to make sure i get there we could do something fun yeah we could do something we could do stand-up comedy um you should just stick to technical stuff you'll just terrify me I don't think I'm never funny on purpose, but I'm often funny. So there you go. I actually, I recently was on another podcast called the Modern CTO Podcast, which is a cool show. And the host is very funny. And he actually, he now spends other than, so he professionally hosts the Modern CTO Podcast.

43:40That's his main job.

43:42Jon Krohn:but his a huge amount of his time uh approaching uh a full-time job is being a stand-up comedian now as well uh so joel beasley uh and it's pretty interesting to hear i think by the time your episode is out my appearance on the modern cto podcast should be out so there's cool things that he talks about in the episode around using data in analytics to and using llms to uh to review all of his standup routines. And so he's trying to get a particular number of laughs per minute from the audience. And he's trying to match. So he's done analytics around what other, you know, professional standup comedians, if you get a Netflix special, how many laughs do you get per minute on average?

44:27Jon Krohn:And so he's trying to work his way up to that. Wow. That's terribly, that reminds me of a story. I had somebody once asked if I would come to their offsite, They were quants. And they're like, can you come to our offsite, talk about graphs and be funny? I was like, you're terrified. I don't. OK, we'll see. So that's a lot of pressure, a lot of pressure when you feel like you have to be. So, yes, you were very diplomatic about your answer, the tools, which I greatly appreciate. And I suspect that that's somewhat related to you being founder and executive director of Graph Geeks. tell us about graph geeks uh how it got started and why someone should reach out to you uh if they need support yeah so graph geeks i love to tell people that i started it because i got lonely but that is actually part part part of the truth so i'd been in the graph space for several years um i don't know over 10 i guess and i have been at several different vendors and when you when When you're working for a vendor, it's wonderful to give you focus, but you also have that focus also gives you a particular way of looking at the graphs landscape and world.

45:46And so when I left the last graph company I was at, I just had a lot of wonderful conversations with people that were either starting things up or had a lesser known, lesser funded approach to graphs and really wanted to highlight that. And the other thing is I was just missing my graphy friends. So the interesting thing about graph folks, they are often a small subset at a company. You usually don't have a 100-person graph team. You sometimes have a one - or five-person graph team. And so we hold on to each other pretty closely. We talk to each other just naturally when we look at the world through relationships.

46:25So we naturally keep our relationships. We help each other out over the years, and we stay in contact. We go to the same conferences. So it's a bit of a tight-knit community. community. And so when I left the vendor space, I missed immediately missed my community and how we looked at things. And I was looking around and I realized there was no vendor agnostic graph community online that I could easily reach out with and interact with on almost a daily basis if I wanted to. So I thought, what the hell? I can start this. If I start this and I fail, nobody can fire me. Why not? And so I started GraphGeeks.

47:03We are graphgeeks.org. If people are looking for us, there is a Discord, a sizable Discord community that helps each other out. So we have a I need help section. We have resources, probably not as many training resources that I would like to get right now, but there are a lot of graph practitioners. So if you're stuck in the middle of a really gnarly graph problem and you're looking for help, you can go on the Discord channel and say, hey, I'm stuck. What have you seen? If you've read a paper, love it, hate it, don't understand it, reach out. If there's somebody you would like to see on the Graph Geeks, either webinar, podcast, what have you, I've got a YouTube channel.

47:49Let me know. I try to get that information out there and help people with things on like, what is the difference between RDF and property graph? We've got a couple hours of that material out there. How do you design to optimize a query? We've got some stuff on that, you know, so there's very, there's a lot of interesting topic, but it's the well is deep. And so, you know, over time, we'll just be adding more and more material. I also have many volunteers and opportunities for volunteers. So if people just want to like geek out, we do that. Yeah. So that's, that's how I got started.

48:26Jon Krohn:Nice work, Amy. It sounds like you're doing an amazing thing for the graph community. You are now an invaluable node in that network. A pivotal node. Call me a pivotal node. A pivotal node. Thank you. So before I let you go, one last technical question that I want to get some insight from you on is what is changing in graphs? You know, what's next? So, you know, we've spent this episode learning about why graphs are cool, what they're useful for. You gave us some direction on tools that we could be grabbing. And so, yeah, like what's next? Some of the things that you mentioned to me before we started recording included multimodal, included graphs for LLM memory and causal graphs.

49:12Jon Krohn:Maybe we could touch on each of those quickly. Yeah, so I'll just, I'll quickly go through the major changes. One is that I already discussed a little bit is framework diversity. So there are like the query engines are getting better. So you don't have to have a database. Different types of graph databases are becoming available. You also have hyperscalers that are getting into reentering the graph space. So lots of choices on framework. So that's a big one. Multimodal, I would put out, well, maybe I should say graphs and AI and what bringing them together is allowing from a use case standpoint.

49:54We talked a bit about that. And then multimodal, which is being able to graph different types of data. So one of the things a colleague of mine, David Hughes, shout out to him, and I do present on is this idea of modeling an image as a graph. And so most of the time we talk about graphs, people think about lexical graphs, so graphs of words or graphs of concepts. Those are the traditional uses. However, you can graph an image. So if we have a picture of me holding my coffee cup, you have the main image is Amy, but there's a coffee cup in front of me to the right. And that relationship has meaning as well.

50:40And so being able to connect those as meaning allows us to do things if we're looking at, for example, and we've done this, looking at a ship, a fleet of ships, and some are ahead of the other. And you can graph that relationship. And then if you look at that relationship over time, you can also estimate the speed. Are those ships coming together? Are they pulling apart? Do they look like they might be antagonistic to each other? So there's all of these things that you can do with different data types. So again, moving to images, we've also added in audio to that. And so for example, we did that with police cars, where you hear them in a video frame, but you don't see them.

51:25And with Doppler effect, you can tell what direction the police cars are heading. And you can do that by graphing it. And to me, that's exciting, not just from a graph rag standpoint, which is what most people want to talk about, like how do I use that with my graph rag, but just this idea of something we have done with graphs forever, which is modeling the relationships between things, we haven't extended it to things in a image, or things in audio. And to me, that just opens up to all sorts of other use cases, like detecting things in sonar, to, again, directional speed in an image, to understand a whole, a grouping in an image of people.

52:10Is there a relationship that we can infer based on how people are standing next to each other? So there's that to me, sorry, multimodal, very, very fascinating area, really cool. But the other one that, or the other two that I would be remiss if I do not mention them first is graph as memory. So graph provides us a way to capture context, and context is really important for AI. And so if you think about the context windows of an agent, they're relatively short right now. So there's a couple of really interesting papers, ZEP, which I have sitting on my desk right now, temporal knowledge graph architecture for agent memory, a must read if you're interested in extending agent memory.

52:57And then MEM0, building production-ready AI agents with scalable long-term memory. Those two papers, really significant, I think, in looking at how you use the context saving ability of a graph to store memory for agents, either for just very simply extending the context window. And you can basically store context and then retrieve it later when you need it or even longer memory. So going beyond a typical context window. That I think is gonna be super hot by the end of the year. If you're into graphs and you haven't thought about graphs as memory for agents, take a look because that's something that I think in six months or less people are gonna be talking about.

53:47Jon Krohn:It is something that's been on my radar as well. That MEM0 paper is something that keeps coming up. So yeah, I agree. Keep an eye on that. The final thing as far as emerging, if we want to add this at some point, is causal graphs. So understanding not just the prediction, being able to predict that something happened, but why it happened, I think is something that in two-ish years will be the next hot thing because we're doing a really good job of predicting the next item in a sequence, but we don't know why that sequence happens. and graphs because you have those two nodes, those circles with an arrow between it, those arrows can, or those links can have, can be an arrow.

54:32And so you can link things in a sequence and you can try to understand influential cause, um, in, you know, whether you're talking about economics or biology or, or what have you. So that's the other area to look out for, but probably a little further ahead.

54:46Jon Krohn:Nice. Thank you for that. Look into the future, even though things move quickly. It does feel like your insights, you know, looking at six, 12 months, maybe even longer are going to end up being really, really helpful. Uh, Amy, this episode has been incredible. You're an absolute pro. It's unsurprising that you host your own podcast, uh, that you do all of this, uh, public facing graph, uh, knowledge distribution work because people, you wouldn't, people wouldn't be able to tell us because we edit all the episodes, but everything in this episode was done in a single take. And so there's been no retakes.

55:24There's been no kind of umming and ahhing,

55:27Jon Krohn:thinking about answers. Amy's just done everything off the cuff flawlessly. It's been a joy recording with you before I let you go. I ask all of my guests for a book recommendation. Do you have one for us? Yes, actually I joined a book club, which I highly recommend joining an old fashioned book club. it's really wonderful to talk to humans about their, what they are thinking. The book is called These Strange New Minds. And it is about LLMs and thinking about them from everything from a technical standpoint to a philosophical standpoint. Are they thinking? Are they not thinking? Do they have the appearance of thinking?

56:05What does thinking mean? And what do we want LLMs to say? How do we look at optimizing and regulating? So I think in this moment in time that we are all in, understanding LLMs a little deeper and from a couple different viewpoints is just a huge benefit. And I highly recommend the book. It's exceptionally well-written.

56:30Jon Krohn:So it's nonfiction. I mean, it's not like a fictionalized... Yeah, yeah. No, no, it is not. It is a multidimensional look at large language models and what it means for models to actually speak back to us. And so this book club that you're in, is this the typical kind of book that you read? Are other people in your book club also kind of data AI people like you are? What's going on here? Yeah. Yes, it is a typical book. We also did one on responsible AI called AI Snake Oil. That's another really good one to look at, but definitely has its opinion. So far, yeah, we've been picking data and AI topics.

57:13And it's a group of us that are in the tech industry. But it's even within the tech industry, these concepts are so large. Having people with different viewpoints, we have somebody from a security background. We have somebody with a responsible AI background, an ethics background. We have people that are just building product. So I think having diverse people and mindsets, people from different countries as well, really shows that even when we have our own opinions on something, there's probably a different way we haven't looked at it. So anyhow, join a book club. Doesn't matter what it's for.

57:53Jon Krohn:It's a great idea. It's something that I, it's on my list of things to do. I hope to get there. I even just reading more, it's something that, yeah, I just, I fantasize just like my fantasy about being under leaves. I also fantasize about being under the leaves of a book. Yeah. Yeah. Yeah. We can talk about that another time because I do think about doing more. It has been very rewarding and it's very useful. So that's why we do these book recommendations at the end of every episode. I know how valuable it is. Even if I would love to read every single book recommendation that I get from my guests, and there's just no possible way I can do it.

58:33Jon Krohn:Fantastic, Amy. So yeah, as I already said a few minutes ago, this has been an amazing episode. You've been an extraordinary communicator. We've already talked about Graph Geeks, which people can visit at graphgeeks.org. Where else should people follow you after this episode to get more of your brilliant thoughts? Well, they can also follow me on LinkedIn. I'm very easy to find. I have an unusual last name. So Amy Hodler, H-O-D-L-E-R, easy to find me there. That's primarily where I post that in I'm on Graph Geeks. Fantastic. Thank you so much, Amy. It has been such a joy to have you on the show.

59:08Jon Krohn:And yeah, hopefully we can get you on again in a few years and see how the graph world has come along. Absolutely. Thank you, John. It's been a real pleasure and I've had a lot of fun and I appreciate all your really insightful questions.

59:22Jon Krohn:Wow, another fun and informative episode today. In it, Amy Hodler covered how graphs capture relationships in data using nodes and edges with properties that include quantities, strengths, and various data types. How graph algorithms like PageRank compute over network topology to reveal insights about structure and behavior that traditional statistical methods miss, making them powerful for applications like fraud detection, supply chain optimization, and recommendation systems. She talked about GraphRag and how it enhances traditional retrieval augmented generation by adding structural context and topology to semantic vector search.

59:57Jon Krohn:And she talked about exciting emerging graph applications, including multimodal graphs, graphs as memory systems for AI agents and causal graphs. As always, you can get all the show notes, including the transcript for this episode, the video recording, any materials mentioned on the show, the URLs for Amy's social media profiles, as well as my own at superdatascience.com slash 923. three. Thanks to everyone on the super data science podcast team, our podcast manager, Sonia Breivich, media editor, Mario Pombo partnerships manager, Natalie Jaisky, our researcher, Serge Massis, writer, Dr. Zara Karche and our founder, Kira Larimenko.

1:00:33Jon Krohn:Thanks to all of them for producing yet another excellent episode for us today for enabling that super team to create this free podcast for you. I encourage you to check out our sponsors. You can support this show by clicking on our sponsors links in the show notes. And if you are interested in sponsoring an episode yourself, you can get the details on how at johnkrone.com slash podcast. Otherwise, share this episode with folks who love it. Review the episode on your favorite podcasting platform or YouTube or wherever you consume podcasts. Subscribe if you're not a subscriber, but most importantly, just keep on listening.

1:01:11Jon Krohn:I'm so grateful to have you listening and I hope I can continue to make episodes you love for years and years to come. Till next time, keep on rocking it out there. And I'm looking forward to enjoying another round of the Super Data Science Podcast with you very soon.

From the publisher

Graphs, but not as you would expect them: Graph analytics guru Amy Hodler speaks to Jon Krohn about the graph data structure and graph applications, graph algorithms, graph RAG, and graphs as memory systems for AI agents. We can use graphs in a surprising number of ways. Money laundering and fraud, as well as supply-chain crime, leave breadcrumbs at multiple “touch-points” over time, behaviors that graphs are better suited to reveal than rows and tables. Amy sees that most interest in graphs has been in the cybersecurity space. But this work isn’t only restricted to fighting crime! Listen to the episode to hear more case examples and how to get into graph work. 

This episode is brought to you by the Dell, by the Intel, by ODSC, the Open Data Science Conference and by Gurobi.

Additional materials: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠www.superdatascience.com/923⁠⁠⁠⁠⁠⁠

Interested in sponsoring a SuperDataScience Podcast episode? Email natalie@superdatascience.com for sponsorship information.

In this episode you will learn:

01:49) A brief history of graphs

(10:08) Uncovering fraud with graphs

(28:31) Where graphs are most commonly applied, to date

(34:49) Retrieval augmented generation graphs

(48:04) The future of graphs

More from Super Data Science: ML & AI Podcast with Jon Krohn

All 130 episodes
923: Graph Algorithms, GraphRAG and Causal Graphs, with Graph Guru Amy HodlerSuper Data Science: ML & AI Podcast with Jon Krohn · 1 h 4 min
Listen in VO