Evidence-backed research demo

Turn research chaos into evidence-backed knowledge maps.

Knowledge Prism helps scholars, research centres, think tanks, and policy teams turn scattered documents into claim reviews, knowledge maps, and audit-ready research briefs.

Problem

Research archives sprawl across PDFs, notes, citations, and folders.

For whom

Scholars, labs, think tanks, supervisors, and policy research teams.

Produces

Knowledge maps, review queues, sample briefs, and audit trails.

Trust

Claims stay tied to source relevance, evidence level, and review status.

Loading current project facts...

Problem

Search finds files. Research still needs judgment.

Researchers have PDFs, Zotero libraries, policy reports, notes, and grey literature scattered across folders. Search can surface documents, but it cannot tell what is trustworthy, what is relevant, what is still only a clue, what needs expert review, or what can enter an explanatory graph.

Who it is for

For people who must defend what they know.

Built for PhD scholars, supervisors, research centres, think tanks, library heads, and policy research teams who need more than a document dump. They need a map of claims, evidence, uncertainty, and interpretive value.

Demonstration snapshot

The International Relations pilot is the proof case.

Read the case study
18works tested
11evidence-backed candidates
14functional interpretations
3review or OCR items
0final graph claims

Method

A research exoskeleton, not an AI replacement.

The scholar keeps the question and the final judgment. The Human Workbench turns source clues into guarded outputs without silently promoting them into verified ontology.

Map the archive

Inventory the corpus and expose what is only metadata.

Test claims

Sample text before treating a generated claim as usable.

Grade evidence

Keep each claim tied to its current level of support.

Interpret function

Ask what the text does for the research question.

Build graph

Connect works, concepts, interactions, and cautions.

Export brief

Carry the review state forward with provenance intact.

Use cases

Where this becomes useful immediately

PhD literature review corpus

Turn scattered reading into a defensible map of arguments, sources, and open questions.

Research centre archive audit

Know what your archive contains, what is usable, and what remains uncertain.

Think tank evidence ledger

Keep policy claims tied to evidence, source, and review status.

Policy-document intelligence

Separate relevant signals from background noise across reports and briefs.

Library/archive modernisation

Move from catalog records to interpretive, auditable knowledge infrastructure.

Outputs

What the user receives

human input workbench corpus inventory evidence dashboard expert review queue functional knowledge graph audit trail exportable reports case-study brief

Trust layer

Every claim carries its luggage.

Every claim keeps its source, evidence grade, relevance decision, functional interpretation, and review status. Metadata can suggest a path, but it is not treated as scholarship. The graph grows only where the evidence can follow.

Trustworthy by design

The demo shows restraint as clearly as it shows capability.

Read the Trust Method
-audit checkpoints
-latest checkpoint
0final graph claims
0final accepted concepts
5public pages linked
Human input becomes guarded output

The Human Workbench accepts a research question, source clue, evidence grade, and functional role, then exports a review note while keeping ontology promotion blocked until provenance is strong.

Public overview first

Visitors begin with the value, then move into the pilot demonstration, method, evidence, and expert machinery only when needed.

Advanced mode is separated

The Expert Dashboard remains available for deep inspection, but it is clearly marked as the advanced evidence cockpit.

Private material stays private

The public demo uses safe exports only. Raw retrieval outputs, raw corpus files, local paths, secrets, and database files are not served.

Machinery, when needed

Start with value. Drill down only when you need the machinery.