been thinking about this after going down a rabbit hole with SillyTavern lorebooks. they work fine for basic stuff but the more complex your world or use case gets, the more you start hitting limits. keyword triggers are fiddly, you’re always fighting token budgets, and updating anything is a pain. started wondering if knowledge graphs are just a cleaner solution to the same problem. from what I can tell the main difference is that lorebooks are basically flat text, that gets shoved into context, whereas a knowledge graph gives you actual structured relationships between entities. so instead of hoping your trigger words fire at the right time, you’re doing proper graph traversal to pull in only what’s actually relevant. the explainability angle is interesting too, you can trace exactly why certain info got retrieved rather than just trusting that the context injection worked. the tradeoff seems to be setup complexity though. Neo4j and GraphRAG aren’t exactly plug and play for most people. reckon the hybrid approach is probably where most people end up, vector search for fuzzy semantic stuff and a graph layer for the structured factual relationships. curious if anyone here has actually tried replacing lorebooks with a proper knowledge graph setup and, whether it was worth the effort, especially for longer running sessions where consistency tends to fall apart.
submitted by /u/Daniel_Janifar
[link] [comments]