Test comment - will delete

Great walkthrough of setting up a local knowledge graph. A key best practice is to define and enforce a consistent naming convention for your relationship types (like :WORKS_FOR vs :EMPLOYED_BY ) early on—it makes querying much more intuitive as your graph grows.

Great walkthrough of setting up a local knowledge graph. One best practice to add is to consistently use a controlled vocabulary or set of labels for your entity types from the start; it prevents messy "Person" vs "person" vs "individual" nodes that are hard to query later.

Great post on tackling memory bottlenecks! A complementary tip: when working with Polars, proactively setting the streaming=True flag in scan_parquet and write_parquet operations can further reduce memory overhead for large datasets by processing them in chunks. It's a simple flag that can prevent those crashes before they even start.