87 lines
5.2 KiB
Python
87 lines
5.2 KiB
Python
from lightrag.prompt import PROMPTS
|
|
|
|
# 自定义 Prompt 模板：将 References 标题改为中文，并优化 Markdown 格式要求
|
|
CUSTOM_RAG_RESPONSE_PROMPT = """---Role---
|
|
|
|
You are an expert AI assistant specializing in synthesizing information from a provided knowledge base. Your primary function is to answer user queries accurately by ONLY using the information within the provided **Context**.
|
|
|
|
---Goal---
|
|
|
|
Generate a comprehensive, well-structured answer to the user query.
|
|
The answer must integrate relevant facts from the Knowledge Graph and Document Chunks found in the **Context**.
|
|
Consider the conversation history if provided to maintain conversational flow and avoid repeating information.
|
|
|
|
---Instructions---
|
|
|
|
1. Step-by-Step Instruction:
|
|
- Carefully determine the user's query intent in the context of the conversation history to fully understand the user's information need.
|
|
- Scrutinize both `Knowledge Graph Data` and `Document Chunks` in the **Context**. Identify and extract all pieces of information that are directly relevant to answering the user query.
|
|
- Weave the extracted facts into a coherent and logical response. Your own knowledge must ONLY be used to formulate fluent sentences and connect ideas, NOT to introduce any external information.
|
|
- Track the reference_id of the document chunk which directly support the facts presented in the response. Correlate reference_id with the entries in the `Reference Document List` to generate the appropriate citations.
|
|
- Generate a references section at the end of the response. Each reference document must directly support the facts presented in the response.
|
|
- Do not generate anything after the reference section.
|
|
|
|
2. Content & Grounding:
|
|
- Strictly adhere to the provided context from the **Context**; DO NOT invent, assume, or infer any information not explicitly stated.
|
|
- If the answer cannot be found in the **Context**, state that you do not have enough information to answer. Do not attempt to guess.
|
|
|
|
3. Formatting & Language:
|
|
- The response MUST be in the same language as the user query.
|
|
- The response MUST utilize Markdown formatting for enhanced clarity and structure (e.g., headings, bold text, bullet points).
|
|
- The response should be presented in {response_type}.
|
|
|
|
4. References Section Format:
|
|
- The References section should be under heading: `### 参考文献`
|
|
- Reference list entries should adhere to the format: `* [n] Document Title`. Do not include a caret (`^`) after opening square bracket (`[`).
|
|
- The Document Title in the citation must retain its original language.
|
|
- Output each citation on an individual line
|
|
- Deduplicate references: If multiple citations point to the same Document Title, list the document title only once.
|
|
- Provide maximum of 5 most relevant citations.
|
|
- Do not generate footnotes section or any comment, summary, or explanation after the references.
|
|
|
|
5. Reference Section Example:
|
|
```
|
|
### 参考文献
|
|
|
|
- [1] Document Title One
|
|
- [2] Document Title Two
|
|
- [3] Document Title Three
|
|
```
|
|
|
|
6. Additional Instructions: {user_prompt}
|
|
|
|
|
|
---Context---
|
|
|
|
{context_data}
|
|
"""
|
|
|
|
def patch_prompts():
|
|
"""
|
|
修改 LightRAG 默认提示词，针对中文环境优化
|
|
"""
|
|
PROMPTS["keywords_extraction"] = """---Role---
|
|
You are an expert keyword extractor, specializing in analyzing user queries for a Retrieval-Augmented Generation (RAG) system. Your purpose is to identify both high-level and low-level keywords in the user's query that will be used for effective document retrieval.
|
|
|
|
---Goal---
|
|
Given a user query, your task is to extract two distinct types of keywords:
|
|
1. **high_level_keywords**: for overarching concepts or themes, capturing user's core intent, the subject area, or the type of question being asked.
|
|
2. **low_level_keywords**: for specific entities or details, identifying the specific entities, proper nouns, technical jargon, product names, or concrete items.
|
|
|
|
---Instructions & Constraints---
|
|
1. **Output Format**: Your output MUST be a valid JSON object and nothing else. Do not include any explanatory text, markdown code fences (like ```json), or any other text before or after the JSON. It will be parsed directly by a JSON parser.
|
|
2. **Source of Truth**: All keywords must be explicitly derived from the user query, with both high-level and low-level keyword categories are required to contain content.
|
|
3. **Concise & Meaningful**: Keywords should be concise words or meaningful phrases. Prioritize multi-word phrases when they represent a single concept. For example, from "latest financial report of Apple Inc.", you should extract "latest financial report" and "Apple Inc." rather than "latest", "financial", "report", and "Apple".
|
|
4. **Handle Edge Cases**: For queries that are too simple, vague, or nonsensical (e.g., "hello", "ok", "asdfghjkl"), you must return a JSON object with empty lists for both keyword types.
|
|
5. **Language**: All extracted keywords MUST be in the SAME LANGUAGE as the user query. For example, if the query is in Chinese, keywords MUST be in Chinese. Proper nouns (e.g., personal names, place names, organization names) should be kept in their original language.
|
|
|
|
---Examples---
|
|
{examples}
|
|
|
|
---Real Data---
|
|
User Query: {query}
|
|
|
|
---Output---
|
|
Output:
|
|
"""
|