DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to merge duplicate entity names into one canonical view with Lemmalog

Assert alias edges and read facts through canonical names, with conflicts escalated instead of silently merged.

Who it is forA researcher or engineer whose extracted facts use several spellings for the same entity and who needs one consistent name for queries.

The problemThe same company or person appears under variant names, so facts split across records and queries miss matches.

The outcomeAlias edges are asserted, closures derive same_as links, and canonical views project facts under one spelling, with topology violations flagged as alias_conflict.

What you need first

  • Rust toolchain with cargo, and a clone of the lemmalog repo
  • Claude Code (or Kimi CLI) installed if you want MCP tools
  • A writable path for the memory snapshot, for example /tmp/lemmalog.snapshot or the default ~/.lemmalog/memory.snap

Steps

  1. Run cargo build --release --features mcp.
  2. Assert alias edges with confidence, for example Acme_Corp --alias_of[0.9]--> Acme, through lemmalog_canonicalize or the CLI observe command.
  3. Query the canonical view, for example current_canon(S, R, O), and check the same_as closure.
  4. Check for alias_conflict facts and resolve any local name that maps to two canonical names.
  5. Retract a wrong alias edge and confirm the downstream views update in the same epoch.

Prompt for your agent

Using the lemmalog MCP server, canonicalize the alias edges in <file> and then query current_canon for <entity>. Expected output: the canonical facts plus any alias_conflict entries. Verify that no local name maps to two canonical names.

Caveat. The canonical rules are described in the README as read-side projections in src/canonical.rs, so check the README example against your own rule set before relying on it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page