> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cortex-labs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Curate world-model lists and resolve identities

> Inspect evidence, correct workspace lists and decide reconciliation proposals without altering source mentions.

You need workspace read access to inspect lists. Contributors can propose changes. An Owner decides proposals, edits lists and starts reconciliation.

## Inspect before changing identity

1. Open the workspace **World Model** and select **Entities** or **Relationships**.
2. Filter by status, type, origin or evidence. Open an entry in the inspector.
3. Read its aliases and cited mentions. Compare identifiers, dates, places and conflicting attributes.
4. Decide whether the evidence supports a correction or needs more investigation.

| Filter | What needs attention |
| - | - |
| New | Extracted entries that no person has reviewed. |
| Other | Extracted types absent from the pinned schema. |
| Added | Entries created by a person. |
| No evidence | Accepted extracted entries with no remaining reachable mention. |
| Unplaced | Geo-layer entries without a supported position for the reader. |
| Hidden | Entries deliberately removed from ordinary selection. |

An entry drawn only by association remains unplaced. An Accepted entry can remain after its evidence expires. Neither state supplies missing source support.

## Propose or make the specific correction

Use the entry's curation controls for the intended action. Record the reason and inspect the affected aliases and relationships.

| Action | Check before deciding |
| - | - |
| Accept or hide | Whether the decision applies to this entry and its visible evidence. Hidden entries remain available for later resolution. |
| Merge | That the entries identify one thing. Select the surviving entry and inspect dependent relationships. |
| Split | Which aliases or evidence belong to each resulting identity. |
| Keep apart | The evidence that similar entries represent different things. This blocks proposed automatic merges. |
| Change type | That the pinned schema contains the intended type. Inspect relationships whose endpoints no longer fit. |
| Place | A supported gazetteer candidate or a deliberate manual pin. Record uncertainty. |

To change a relationship's type, hide it and add the intended relationship. Source mentions remain unchanged.

## Review reconciliation proposals

An Owner opens **Reconcile runs**, chooses a permitted enrichment model and selects the number of passes. Start one manageable run.

Inspect its progress and stored model answers. The run proposes merges and types for **Other** entries. It does not apply them.

Open **Review queue** and filter by the run. Inspect each proposal, cited mentions, reason and confidence. Use **Verdict → Accept** or **Reject**. For larger merge groups, inspect **Remove one entry** before deciding.

Acceptance rechecks the current entries. Changed types, missing entries or a keep-apart rule can supersede a stale proposal. Rejected or removed group entries are kept apart from the proposed survivor.

A newer reconciliation supersedes earlier open run proposals. Confirm the run filter before a bulk acceptance.

## Verify and undo when needed

Reopen the affected entries and inspect **Edit log**. Check the surviving identity, aliases, placement and evidence.

Undo later edits on the same entries before undoing an earlier dependent edit. Undo does not reopen its decided proposal.

See [Mentions, entities and relationships](/vantage/explore-evidence/mentions-entities-relationships) for the evidence boundary.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.