426 karma · joined January 2, 2025
How do you handle conflict resolution when multiple users modify the same issue or thread concurrently across remotes? Is it purely Git's merge mechanics, or do you apply any domain-specific heuristics?
having been work with both json and pb, and i'd say pb is pretty solid.
how is this better than PB?
Is it due to the model's training distribution (mostly single-shot completions), the way context windows are encoded, or an architectural bottleneck?
Feels like there's no dynamic internal state that evolves over the conversation — only a repeated re-parsing of static history. Has anyone seen work on integrating memory/state mechanisms that allow belief revision within a session, not just regurgitation of past tokens?
Neo4j also supports building embedding leveraging more information in the graph in addition to single node's property: https://neo4j.com/docs/graph-data-science/current/machine-le... (It's hard to incrementally compute them, but users can still compute them after the graph is built)
looking forward to learn your thoughts :)
- Metadata based match (I’ve done that with search system in the past)
- Embedding base match (false positive is definite consideration
- Using knowledge graph itself to do entity resolution before feeding the entities to graph next
Add human in the loop to guide entity resolutions.
What do you think? Would love to learn your thoughts:)
- Structured data - this is probably more close to the use case you mention
- Unstructure data and extract relationship and build KG with natural language understanding - which is this article trying to explore. Here is a paper discussing about this https://arxiv.org/abs/2409.13731
In general it is an alternative way to establish connections with entities easily. And these relationships could help with discovery, recommendation and retrieval. Thanks @alexchantavy for sharing use-cases in security.
Would love to learn more from the community :)