Knowledge network
Hold the entities and relationships found in your documents next to their sources, in a structure staff can browse and correct rather than a hidden memory.
Updated 21 Aug 2026
Definition
A knowledge network outlives the conversation and can be corrected, which chat history cannot. You can browse the entities, concepts, relationships and ontology it holds, and merge duplicates. That it exists does not mean what it extracted is right.
Use it when useful context spans documents and conversations and the organisation needs a durable, correctable structure rather than a transient chat history.
If users only need to find current documents or answer a narrow question, a maintained graph may add unnecessary curation cost. Work out what you would use the structure for before you build it.
Marella has screens for concepts, entities, relationships, ontology, folders and merging duplicates, and runs a scheduled maintenance pass whose changes you can review.
Use approved source documents with a small reference set of expected entities and relationships. Review both extraction quality and whether the structure improves the target research task.
Agree who curates terminology, which users can change structures, how source deletion propagates and whether scheduled maintenance proposes or applies changes in the selected configuration.
It uses entities and relationships, while Marella's product layer also includes concepts, ontology, folders and curation workflows. Evaluate the specific structures you need.
Extraction and scheduled maintenance mechanisms exist, but quality, review gates and configuration must be inspected. Automatic change is not the same as improvement.
The organisation defines and curates the terminology relevant to its workflow, subject to the roles and operating model agreed for the deployment.
Choose a bounded source set and define the entities, relationships and correction tasks reviewers should expect.