> ## Documentation Index > Fetch the complete documentation index at: https://docs.pnbr.io/llms.txt > Use this file to discover all available pages before exploring further. # Two entities in the Graph are one thing > Penumbra has no operation that merges two entities, so you move the relationships to the one you keep and then delete the other. Troubleshooting · graph > **Use when** > > Two entities that are already in the Graph describe the same thing, and each holds some relationships, properties or citations. > **Looking for something else?** > > An item in a workspace that repeats a Graph entity (problem [An extraction found an entity the Graph already has](https://docs.pnbr.io/troubleshooting/extraction-duplicates-existing-entity.md)). Two entities that may be different things (problem [Two entities have the same name](https://docs.pnbr.io/troubleshooting/same-name-two-entities.md)). ## Signs * A search returns two entities of one type for one thing, with different ids. * Each entity has some of the relationships that the one thing should have. * A read of one entity misses a fact, a relationship or a citation that the other holds. ## Why it happens Each entity has its own id, relationships and citations. Penumbra keeps no tie between two entities, so it does not know they are one thing. A repeat of capture or extraction, with no search first, makes the second entity. ## What Penumbra does By itself: * Deletes an entity softly. The entity keeps its history, and you can restore it by id. * Deletes the relationships that touch the entity with it. * Restores the entity only, with no approval wait. It does not bring back the relationships. * Keeps the stored citations of a deleted entity. `read` with `entity:` still shows its last properties and citations, marked deleted. * Holds a delete made with an API key or as a connected agent until an owner or admin approves it. A person's own session does not wait. You must: * Choose the entity to keep, and write down what the other holds. * Stage a new relationship on the kept entity for each one you keep. * Carry over the properties and citations you want, then delete the other entity. * Check each part. Not handled: * No merge operation exists in the CLI, the MCP tools, the Program methods or the SDK. * No operation moves a relationship to another entity, because its ends never change. * Penumbra does not copy properties, citations or times from one entity to the other. * Nothing sends the id of the deleted entity to the kept one. ## Do 1. Confirm the two are one thing (problem [same-name-two-entities](https://docs.pnbr.io/troubleshooting/same-name-two-entities.md)). 2. Follow recipe [resolve-duplicates](https://docs.pnbr.io/guides/resolve-duplicates.md). It stages the new relationships, carries over properties and deletes the extra entity in one workspace. 3. If a delete waits for approval, give the person the approval URL and stop (problem [change-waits-for-approval](https://docs.pnbr.io/troubleshooting/change-waits-for-approval.md)). ## Don't * Don't delete the extra entity before you stage its relationships on the kept one. The delete removes them, and a restore does not bring them back. * Don't name the ends of the new relationships by name. Duplicates make a name fail with `node_ambiguous`. Use ids. * Don't tell the person it is merged until you have checked each part below. * Don't send the delete again while it waits (problem [change-waits-for-approval](https://docs.pnbr.io/troubleshooting/change-waits-for-approval.md)). ## Check 1. The kept entity has each relationship you listed: `penumbra graph edges --node --direction both`. 2. The kept entity has each property you carried over: `penumbra graph get `. 3. The kept entity lists the Files you cited: `penumbra context entity --json`. 4. The extra entity is deleted: `penumbra graph get ` prints a `deleted:` line. 5. A search by the name returns the kept entity only: `penumbra graph search "" --type `. ## Related Recipe [resolve-duplicates](https://docs.pnbr.io/guides/resolve-duplicates.md). Card rules [entity.3](https://docs.pnbr.io/concepts/entity.md#rule-entity-3), [entity.4](https://docs.pnbr.io/concepts/entity.md#rule-entity-4), [relationship.4](https://docs.pnbr.io/concepts/relationship.md#rule-relationship-4), [relationship.6](https://docs.pnbr.io/concepts/relationship.md#rule-relationship-6) and [relationship.8](https://docs.pnbr.io/concepts/relationship.md#rule-relationship-8). Problem [same-name-two-entities](https://docs.pnbr.io/troubleshooting/same-name-two-entities.md). Problem [extraction-duplicates-existing-entity](https://docs.pnbr.io/troubleshooting/extraction-duplicates-existing-entity.md). Problem [change-waits-for-approval](https://docs.pnbr.io/troubleshooting/change-waits-for-approval.md). ## Keep going [Entity](https://docs.pnbr.io/concepts/entity.md) · [Relationship](https://docs.pnbr.io/concepts/relationship.md) · [Workspace](https://docs.pnbr.io/concepts/workspace.md) · [Approval](https://docs.pnbr.io/concepts/approval.md) · [Make two entities one](https://docs.pnbr.io/guides/resolve-duplicates.md) · [Two entities have the same name](https://docs.pnbr.io/troubleshooting/same-name-two-entities.md) · [An extraction found an entity the Graph already has](https://docs.pnbr.io/troubleshooting/extraction-duplicates-existing-entity.md) Penumbra Grammar 0.6.26 This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.