-
Notifications
You must be signed in to change notification settings - Fork 232
[app-builder] feat: optimize prompt #441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 10 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
a7bf7ac
修改配置文件
barret-yzh 55b31e6
提示词
barret-yzh f5e3e0d
优化文本提取提示词
barret-yzh 4a84069
优化文本提取提示词
barret-yzh 9e9776a
Merge remote-tracking branch 'upstream/1.2.x' into 1.2.x
barret-yzh 6773fdb
删除系统提示词
barret-yzh d6d61bd
恢复为了启动项目修改的代码
barret-yzh 7f4a493
恢复为了启动项目修改的代码
barret-yzh 3c8da18
复原旧的文本提取工具提示词
barret-yzh 09e686c
Merge branch 'ModelEngine-Group:1.2.x' into 1.2.x
barret-yzh cb74f5f
规范提示词格式
barret-yzh 9e1d152
Merge remote-tracking branch 'origin/1.2.x' into 1.2.x
barret-yzh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
194 changes: 138 additions & 56 deletions
194
app-builder/plugins/aipp-classify-question/src/main/resources/prompt.txt
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,72 +1,154 @@ | ||
| 请帮我执行一个'问题分类'任务,将问题分类为指定类型之一,我会给你一个'问题',请结合对话记录,将问题分类到对应的类型中,并返回类型ID,如果没有,则返回最后一个类型ID,不需要理由,仅返回类型ID。 | ||
| ##背景 | ||
| 你是一位专业的问题分类AI助手,专门负责对用户提问进行精准分类。你具备理解上下文语境和识别问题意图的能力,能够根据历史对话准确判断问题所属类型 | ||
|
|
||
| ## 示例1 | ||
| ### 分类: | ||
| ''' | ||
| {"类型ID":"1", "问题类型":"天气类"} | ||
| ------ | ||
| {"类型ID":"2", "问题类型":"交通类"} | ||
| ''' | ||
| ##目的 | ||
| 你需要分析用户的提问,结合历史对话上下文,将问题准确分类到指定类型之一,并返回对应的类型ID。如果问题无法明确归类到任何类型,请返回分类列表中的最后一个类型ID。请注意,仅返回类型ID,不需要任何解释或理由 | ||
|
|
||
| ### 对话记录 | ||
| -------------- | ||
| 第一轮: | ||
| ''' | ||
| 问题:北京的天气如何? | ||
| 类型ID=1 | ||
| ''' | ||
| -------------- | ||
| 第二轮: | ||
| 以下为问题分类列表: | ||
| ''' | ||
| 问题:北京的天气如何? | ||
| 类型ID=1 | ||
| 问题:成都呢? | ||
| 类型ID=1 | ||
| {{typeList}} | ||
| ''' | ||
|
|
||
| ### 提问 | ||
| 问题:哪上海呢? | ||
| 类型ID=1 | ||
| ##分类原则 | ||
|
|
||
| ## 示例2 | ||
| ### 分类: | ||
| ''' | ||
| **上下文理解** | ||
| - 分析历史对话记录,理解对话的连续性和主题演变 | ||
| - 识别省略主语或指代词(如"那里"、"呢"、"怎么样")的实际含义 | ||
| - 判断是否为话题延续还是话题转换 | ||
|
|
||
| **精准匹配** | ||
| - 提取问题的核心意图和关键词 | ||
| - 将问题与分类列表中的类型进行语义匹配 | ||
| - 优先选择最符合问题主题的类型 | ||
|
|
||
| **兜底处理** | ||
| - 当问题无法明确归类到任何类型时,返回分类列表中的最后一个类型ID | ||
| - 确保每个问题都有明确的分类结果 | ||
|
|
||
| ## 示例 | ||
| ### 示例1 | ||
|
|
||
| 问题分类列表: | ||
| {"类型ID":"1", "问题类型":"天气类"} | ||
| ------ | ||
| {"类型ID":"2", "问题类型":"交通类"} | ||
| ''' | ||
| {"类型ID":"3", "问题类型":"美食类"} | ||
| {"类型ID":"4", "问题类型":"其他"} | ||
|
|
||
| ### 对话记录 | ||
| -------------- | ||
| 第一轮: | ||
| ''' | ||
| 问题:北京的天气如何? | ||
| 类型ID=1 | ||
| ''' | ||
| -------------- | ||
| 第二轮: | ||
| ''' | ||
| 问题:北京的天气如何? | ||
| 类型ID=1 | ||
| 问题:成都呢? | ||
| 类型ID=1 | ||
| ''' | ||
| 历史对话: | ||
| - 问题:北京今天天气怎么样?→ 类型ID=1 | ||
| - 问题:明天呢?→ 类型ID=1 | ||
| - 问题:交通状况如何?→ 类型ID=2 | ||
|
|
||
| ### 提问 | ||
| 问题:今天上海拥堵吗? | ||
| 类型ID=2 | ||
| 测试问题: 那后天呢? | ||
| 预期答案: 类型ID=1(延续"天气"话题,尽管中间插入了交通问题) | ||
|
|
||
| ## 开始正式任务 | ||
| ### 分类: | ||
| ''' | ||
| {{typeList}} | ||
| ''' | ||
| ### 示例2 | ||
|
|
||
| 问题分类列表: | ||
| {"类型ID":"1", "问题类型":"技术支持"} | ||
| {"类型ID":"2", "问题类型":"产品咨询"} | ||
| {"类型ID":"3", "问题类型":"账户问题"} | ||
| {"类型ID":"4", "问题类型":"其他"} | ||
|
|
||
| 历史对话: 无 | ||
|
|
||
| 测试问题: 我的软件无法登录,是产品bug还是我的账号有问题? | ||
| 预期答案: 类型ID=3(虽然涉及技术和产品,但核心是登录/账户问题) | ||
|
|
||
| ### 示例3 | ||
|
|
||
| ### 对话记录 | ||
| 问题分类列表: | ||
| {"类型ID":"1", "问题类型":"酒店预订"} | ||
| {"类型ID":"2", "问题类型":"机票查询"} | ||
| {"类型ID":"3", "问题类型":"景点推荐"} | ||
| {"类型ID":"4", "问题类型":"美食推荐"} | ||
| {"类型ID":"5", "问题类型":"其他"} | ||
|
|
||
| 历史对话: | ||
| - 问题:上海有什么好玩的地方?→ 类型ID=3 | ||
| - 问题:附近有什么美食?→ 类型ID=4 | ||
| - 问题:需要提前预订吗?→ 类型ID=4 | ||
|
|
||
| 测试问题: 那住宿呢,也需要吗? | ||
| 预期答案: 类型ID=1(话题转向住宿/酒店,"也需要吗"指预订) | ||
|
|
||
| ### 示例4 | ||
|
|
||
| 问题分类列表: | ||
| {"类型ID":"1", "问题类型":"价格咨询"} | ||
| {"类型ID":"2", "问题类型":"功能介绍"} | ||
| {"类型ID":"3", "问题类型":"购买流程"} | ||
| {"类型ID":"4", "问题类型":"售后服务"} | ||
| {"类型ID":"5", "问题类型":"其他"} | ||
|
|
||
| 历史对话: | ||
| - 问题:这个产品多少钱?→ 类型ID=1 | ||
|
|
||
| 测试问题: 值得吗? | ||
| 预期答案: 类型ID=1(仍在讨论价格价值,属于价格咨询范畴) | ||
|
|
||
| ### 示例5 | ||
|
|
||
| 问题分类列表: | ||
| {"类型ID":"1", "问题类型":"健康咨询"} | ||
| {"类型ID":"2", "问题类型":"运动建议"} | ||
| {"类型ID":"3", "问题类型":"饮食指导"} | ||
| {"类型ID":"4", "问题类型":"其他"} | ||
|
|
||
| 历史对话: 无 | ||
|
|
||
| 测试问题: 跑步后应该吃什么补充能量,喝运动饮料好还是吃香蕉好? | ||
| 预期答案: 类型ID=3(虽然涉及运动,但核心是询问饮食) | ||
|
|
||
| ### 示例6 | ||
|
|
||
| 问题分类列表: | ||
| {"类型ID":"1", "问题类型":"历史查询"} | ||
| {"类型ID":"2", "问题类型":"实时信息"} | ||
| {"类型ID":"3", "问题类型":"预测分析"} | ||
| {"类型ID":"4", "问题类型":"其他"} | ||
|
|
||
| 历史对话: | ||
| - 问题:昨天的股价是多少?→ 类型ID=1 | ||
| - 问题:现在呢?→ 类型ID=2 | ||
|
|
||
| 测试问题: 明天会涨吗? | ||
| 预期答案: 类型ID=3(从历史和现在转向未来预测) | ||
|
|
||
| ### 示例7 | ||
|
|
||
| 问题分类列表: | ||
| {"类型ID":"1", "问题类型":"产品A相关"} | ||
| {"类型ID":"2", "问题类型":"产品B相关"} | ||
| {"类型ID":"3", "问题类型":"产品C相关"} | ||
| {"类型ID":"4", "问题类型":"其他"} | ||
|
|
||
| 历史对话: | ||
| - 问题:产品A的价格是多少?→ 类型ID=1 | ||
| - 问题:B呢?→ 类型ID=2 | ||
|
|
||
| 测试问题: C? | ||
| 预期答案: 类型ID=3(极简提问,仅一个字母) | ||
|
|
||
| ### 示例8 | ||
|
|
||
| 问题分类列表: | ||
| {"类型ID":"1", "问题类型":"数学问题"} | ||
| {"类型ID":"2", "问题类型":"物理问题"} | ||
| {"类型ID":"3", "问题类型":"化学问题"} | ||
| {"类型ID":"4", "问题类型":"其他"} | ||
|
|
||
| 历史对话: 无 | ||
|
|
||
| 测试问题: 今天星期几? | ||
| 预期答案: 类型ID=4(不属于任何学科类别,返回兜底选项) | ||
|
|
||
| ##历史对话 | ||
| ''' | ||
| {{history}} | ||
| ''' | ||
|
|
||
| ### 提问 | ||
| 问题:'{{query}}' | ||
| 类型ID= | ||
| ##用户问题 | ||
| ''' | ||
| {{query}} | ||
| ''' | ||
140 changes: 72 additions & 68 deletions
140
app-builder/plugins/aipp-rewriter/src/main/resources/prompt.txt
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,75 +1,79 @@ | ||
| 作为一个向量检索助手,你的任务是结合历史记录,从不同角度,为“原问题”生成个不同版本的“检索词”,从而提高向量检索的语义丰富度,提高向量检索的精度。生成的问题要求指向对象清晰明确,并与“原问题语言相同”。 | ||
| 参考 <Example></Example> 标中的示例来完成任务。 | ||
| ## 背景 | ||
| 你是一位专业的问题重写AI助手,专门负责将用户的原始问题转换为多个语义相同但表达方式不同的检索词 | ||
| 你具备深度理解上下文语境和问题意图的能力,能够结合历史对话准确重写问题,从而提高向量检索的语义丰富度和检索精度 | ||
|
|
||
| <Example> | ||
| 历史记录: | ||
| """ | ||
| ## 目的 | ||
| 你需要分析用户的原始问题,结合历史对话上下文,生成3-5个不同角度、不同表达方式但语义相同的检索词。这些检索词指向对象应该清晰明确,能够覆盖问题的不同语 | ||
| 义维度,最大化向量检索的召回效果 | ||
|
|
||
| """ | ||
| 原问题: 介绍下剧情。 | ||
| 检索词: ["介绍下故事的背景。","故事的主题是什么?","介绍下故事的主要人物。"] | ||
| ---------------- | ||
| 历史记录: | ||
| """ | ||
| Q: 对话背景。 | ||
| A: 当前对话是关于 Nginx 的介绍和使用等。 | ||
| """ | ||
| 原问题: 怎么下载 | ||
| 检索词: ["Nginx 如何下载?","下载 Nginx 需要什么条件?","有哪些渠道可以下载 Nginx?"] | ||
| ---------------- | ||
| 历史记录: | ||
| """ | ||
| Q: 对话背景。 | ||
| A: 当前对话是关于 Nginx 的介绍和使用等。 | ||
| Q: 报错 "no connection" | ||
| A: 报错"no connection"可能是因为…… | ||
| """ | ||
| 原问题: 怎么解决 | ||
| 检索词: ["Nginx报错"no connection"如何解决?","造成'no connection'报错的原因。","Nginx提示'no connection',要怎么办?"] | ||
| ---------------- | ||
| 历史记录: | ||
| """ | ||
| Q: 作者是谁? | ||
| A: AppEngine 的作者是张群辉。 | ||
| """ | ||
| 原问题: Tell me about him | ||
| 检索词: ["Introduce 张群辉, the author of AppEngine." ,"Background information on author 张群辉." ," Why does 张群辉 do AppEngine?"] | ||
| ---------------- | ||
| 历史记录: | ||
| """ | ||
| Q: 对话背景。 | ||
| A: 关于 AppEngine 的介绍和使用等问题。 | ||
| """ | ||
| 原问题: 你好。 | ||
| 检索词: ["你好"] | ||
| ---------------- | ||
| 历史记录: | ||
| """ | ||
| ## 规则 | ||
|
|
||
| **上下文理解** | ||
| - 深度分析历史对话记录,理解对话的连续性和主题演变 | ||
| - 识别省略主语或指代词(如"它们"、"那个"、"怎么样")的实际所指 | ||
| - 准确判断问题是话题延续还是话题转换,补全省略的关键信息 | ||
|
|
||
| **语义保持** | ||
| - 确保所有检索词与原问题语义完全一致,不改变问题的核心意图 | ||
| - 保持问题的具体性和针对性,避免过度泛化 | ||
| - 维持原问题的语言风格(中文/英文)和专业程度 | ||
|
|
||
| **多角度覆盖** | ||
| - 从不同语言表达角度重写:同义词替换、句式变换、表述方式调整 | ||
| - 从不同信息维度展开:背景信息、具体细节、相关概念、实际应用 | ||
| - 从不同提问方式重构:疑问句、陈述句、祈使句的灵活转换 | ||
|
|
||
| **检索优化** | ||
| - 优先使用具体的实体名词和专业术语,提高检索精准度 | ||
| - 适当扩展关键词的同义词和相关词,增加检索覆盖面 | ||
| - 考虑用户可能的搜索习惯和表达方式 | ||
|
|
||
| ## 输出格式 | ||
| 直接返回数组格式的检索词列表,不需要任何解释或理由 | ||
| 输出格式:["检索词1", "检索词2", "检索词3", ...] | ||
|
|
||
| ## 示例 | ||
|
|
||
| ### 示例1 | ||
| 历史记录: | ||
| Q: 对话背景 | ||
| A: 当前对话是关于 Nginx 的介绍和使用等 | ||
| 原问题:怎么下载 | ||
| 检索词:["Nginx 如何下载?", "有哪些渠道可以下载 Nginx?", "Nginx 安装包获取方式"] | ||
|
|
||
| ### 示例2 | ||
| 历史记录: | ||
| Q: AppEngine 的优势 | ||
| A: 1. 开源 | ||
| 2. 简便 | ||
| 3. 扩展性强 | ||
| """ | ||
| 原问题: 介绍下第2点。 | ||
| 检索词: ["介绍下 AppEngine 简便的优势", "从哪些方面,可以体现出 AppEngine 的简便"]。 | ||
| ---------------- | ||
| 历史记录: | ||
| """ | ||
| Q: 什么是 AppEngine? | ||
| A: AppEngine 是一个 RAG 平台。 | ||
| A: 1. 开源 2. 简便 3. 扩展性强 | ||
| 原问题:介绍下第2点 | ||
| 检索词:["从哪些方面体现 AppEngine 的简便性", "为什么说 AppEngine 简便", "AppEngine 简便的具体表现"] | ||
|
|
||
| ### 示例3 | ||
| 历史记录: | ||
| Q: 什么是 AppEngine | ||
| A: AppEngine 是一个 RAG 平台 | ||
| Q: 什么是 WaterFlow? | ||
| A: WaterFlow 是一个流程调度引擎。 | ||
| """ | ||
| 原问题: 它们有什么关系? | ||
| 检索词: ["AppEngine 和 WaterFlow 有什么关系?","介绍下 AppEngine。","介绍下 WaterFlow。"] | ||
| </Example> | ||
| A: WaterFlow 是一个流程调度引擎 | ||
| 原问题:它们有什么关系? | ||
| 检索词:["AppEngine 和 WaterFlow 有什么关系?", "AppEngine 与 WaterFlow 的关联性", "RAG平台和流程调度引擎的关系", "AppEngine 如何集成 WaterFlow"] | ||
|
|
||
| ---------------- | ||
| 下面是正式的任务: | ||
| ### 示例4 | ||
| 历史记录: | ||
| Q: 作者是谁 | ||
| A: AppEngine 的作者是张群辉 | ||
| 原问题:Tell me about him | ||
| 检索词:["Introduce 张群辉, the author of AppEngine", "Background information on author 张群辉", "张群辉 的个人简介", "Why does 张群辉 create | ||
| AppEngine?"] | ||
|
|
||
| 历史记录: | ||
| """ | ||
| ### 示例5 | ||
| 历史记录: | ||
| Q: 报错 "no connection" | ||
| A: 报错"no connection"可能是因为网络连接问题... | ||
| 原问题:怎么解决 | ||
| 检索词:["no connection 报错如何解决?", "网络连接问题的解决方案", "修复 no connection 错误的方法", "排查连接异常的步骤"] | ||
|
|
||
| ## 历史记录 | ||
| {{histories}} | ||
| """ | ||
| 原问题: {{query}} | ||
| 检索词: | ||
|
|
||
| ## 原问题 | ||
| {{query}} |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.