Skip to content
Project guidePublic repo reviewed

WeKnora Support Knowledge Base: Upload Docs and Verify Citations

A small acceptance record showing which questions have clear source support, which need better documentation, and which require human review.

Use caseTurn CSV, documents, or search results into reviewable data

Source · Tencent/WeKnoraIntermediate18 min

Use three fictional support documents to test WeKnora with answerable, unsupported, and conflicting questions, then inspect each citation against the source.

Source · Tencent/WeKnora · Open-source walkthrough

A support answer can sound plausible while pointing to the wrong policy version. This walkthrough builds a small test knowledge base and checks whether answers lead back to the right source. It does not connect a live customer system or send model output to customers.

  • Docker Compose plus configured chat and embedding models. WeKnora is MIT licensed; model, embedding, or document-processing services may have separate costs.
  • Prepare three fictional documents covering returns, delivery, and warranty. Do not start with real orders, phone numbers, or customer conversations.

Screenshot of the Q&A interface from Tencent WeKnora’s repository, showing project sample data; it is not a JevLog deployment or test. Source: original screenshot.

Screenshot of the Q&A interface from Tencent WeKnora’s repository, showing project sample data; it is not a JevLog deployment or test. Source: original screenshot.

Follow Tencent WeKnora’s official quick start: clone the repository, copy .env.example, configure a model, and start the base Docker Compose stack. For the first document Q&A, skip optional graph, Wiki, and skill-sandbox services.

Create a support test knowledge base, upload the three fictional documents, and wait until each file is fully parsed. Add a version or effective date to policy documents so old and current rules are easy to distinguish.

Ask one question answered by the documents, one question they do not cover, and one question where old and new rules conflict. Open each citation and compare the cited text and date with the answer. A citation is a lead to verify, not proof that the answer is correct.

If a citation points to the wrong passage, inspect the parsed chunks for that document. WeKnora supports chunk editing with version history. Correct the source and rerun the same questions. Route unclear or conflicting policies to a person.

A small acceptance record showing which questions have clear source support, which need better documentation, and which require human review.

  • An answerable question points to the correct file and passage.
  • An unsupported question is not treated as confirmed policy.
  • A policy conflict is sent for human review with the applicable version recorded.