[BUG] Custom edges not getting picked up

[GioPetro]

Bug Description

Graphiti_core v20.4
Passing custom entities works
Passing custom relationships (edges) does not work!

EDGE_TYPE_MAP = {
    # Primary prediction relationships (CORE BUSINESS LOGIC)
    ("DetectedItemEntity", "CanonicalItemEntity"): ["ItemMatchesCanonical"],
    ("DetectedInvoiceEntity", "CanonicalItemEntity"): ["InvoiceContextInformsCanonical"],
    ("SupplierEntity", "CanonicalItemEntity"): ["SupplierInfluencesCanonical", "SupplierSellsItem"],

    # Invoice-level context relationships
    ("InvoiceEntity", "SupplierEntity"): ["InvoiceIssuedBySupplier"],
    ("InvoiceEntity", "DetectedInvoiceEntity"): ["InvoiceMatchesDetected"],
    ("InvoiceEntity", "CanonicalItemEntity"): ["InvoiceContainsCanonicalItem"],
    ("InvoiceEntity", "DetectedItemEntity"): ["InvoiceContainsDetectedItem"],
    
    # Cross-source context relationships
    ("SupplierEntity", "DetectedInvoiceEntity"): ["SupplierMatchesDetected"],
}

<more code>

await graphiti.add_episode(
        name=episode_name,
        episode_body=episode_body,
        source=EpisodeType.json,
        source_description=f"Single entity ingestion for invoice {doc_code}",
        reference_time=datetime.now(timezone.utc),
        edge_type_map=EDGE_TYPE_MAP,
        entity_types=ENTITY_TYPES,
        edge_types=EDGE_TYPES,

    )

<more code>

await graphiti.add_triplet(
        EntityNode(uuid=invoice_entity["id"], name="InvoiceEntity", group_id=doc_code),
        edge,
        EntityNode(uuid=supplier_entity["id"], name="SupplierEntity", group_id=doc_code)
    )

I'm trying to pass these, using Gemini models, I'm even trying gemini-2.5-pro with no difference in picking it up.
I am concluding there is somethig wrong within the graphiti_core library.
The default edges, "Mentions" and "Relates_To" do have some of the attributes I mention in adding triplet facts too, like
name ="HAS_CATEGORY"
but I am not sure this is supposed to be working.

I am in desperate mode to make this work as intended. I have been trying for a good solid 3 months.
Need assistance, am I missing something??? Doubt, must be a bug

[nilaypatel99]

Hi petro these is how mostly it is stored
In Graphiti, custom edge types are stored in the name field — and this field is treated as the edge type everywhere in the system. This design choice isn’t arbitrary; it’s all about performance and compatibility with Neo4j and other GraphDBs. Using a standardized field for edge type allows us to define search indices and build efficient Cypher queries consistently. While this is technically an implementation detail, it’s an important one that keeps Graphiti fast and predictable. As a bonus, you can also set the name value to be the display label for edges in the Neo4j app, making your visualizations easier to interpret.

[GioPetro]

Many thanks. Good clarification, maybe worth putting it on the docs as a sidenote.
"Name" attribute on an edge, is where the custom relationships are set.
Thanks, closing.

[haimgia]

Hi, I'm having the same issue as GioPetro where my custom edges are not showing on http://localhost:3000. I'm using falkordb/falkordb:latest to run the server. I'm testing out examples.podcast.podcast_runner.py and I don't see the custom relationships, only custom entities. The structure is the same as GioPetro's code except I'm not calling add_triplet.

Do I need to call add_triplet after calling add_episode? Can you also clarify how you're storing the custom edge in the name field? An example would be greatly appreciated.

[GioPetro]

No need for add_triplet, I'm doing for my use case.
Essentially, on the discord server I got the answer.

We are doing things correctly. The custom relationships are under the "name" attribute of the "RELATES_TO" edge you see on the graph db. So, in other words, the "relationships" are not custom relationships, and defining custom ones, means the "name" value of that changes.
Took me a while to understand, because I was indeed seeing the "name" being my custom relationships, though I thought it shouldn't be like that.
It's a misconception between "relationships".

Hope that helps!

[haimgia]

Thanks, that did help! Also, thank you for mentioning that there was a Discord server. Will start to refer to that more often.

…

On Mon, Sep 15, 2025 at 2:19 PM George Petropoulos ***@***.***> wrote: *GioPetro* left a comment (getzep/graphiti#903) <#903 (comment)> No need for add_triplet, I'm doing for my use case. Essentially, on the discord server I got the answer. We are doing things correctly. The custom relationships are under the "name" attribute of the "RELATES_TO" edge you see on the graph db. So, in other words, the "relationships" are not custom relationships, and defining custom ones, means the "name" value of that changes. Took me a while to understand, because I was indeed seeing the "name" being my custom relationships, though I thought it shouldn't be like that. It's a misconception between "relationships". Hope that helps! — Reply to this email directly, view it on GitHub <#903 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASTDUPQYZP7HBDZBROMYQVT3S37L7AVCNFSM6AAAAACGDQJFHOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEOJTGM4TGMBQGA> . You are receiving this because you commented.Message ID: ***@***.***>