✨ feat: 记忆排除规则新增设备状态查询、故障报告、联系方式查找
- 新增排除类别:设备/设施状态查询与结果、Bug/故障报告、联系方式查找 - 新增3个日语负例 few-shot examples Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
bb23d230d1
commit
7da8466b3d
@ -29,6 +29,12 @@ Types of Information to EXCLUDE (Do NOT remember these):
|
||||
- Examples: "今日の天気は25度", "株価は150ドル", "会議室は空いている"
|
||||
5. **Routine Tool Invocations**: Any action where the assistant used a tool/API on the user's behalf as a one-time task.
|
||||
- Examples: "カレンダーAPIを呼び出した", "データベースを検索した", "ファイルを開いた"
|
||||
6. **Equipment/Facility Status Inquiries and Results**: When the user asks about the status of equipment, rooms, or facilities, or when the assistant reports back equipment status details.
|
||||
- Examples: "DR1の照明状態について問い合わせた", "DR1の照明は遠藤照明製でオフライン状態", "会議室の空調が故障中"
|
||||
7. **Bug Reports and Troubleshooting**: When the user reports a malfunction, bug, or issue with equipment or systems.
|
||||
- Examples: "ミュートボタンに不具合がある", "静音ボタンが使えない", "Wi-Fiが繋がらない"
|
||||
8. **Contact Information Lookups**: When the user asks to find someone's phone number, email, or contact details.
|
||||
- Examples: "コンシェルジュの電話番号を探している", "田中さんのメールアドレスを調べた"
|
||||
|
||||
**IMPORTANT - Plain Language Rule**: All extracted facts MUST be written in plain, everyday language that anyone can understand. Do NOT use structured formats like "Contact:", "referred as", "DEFAULT when user says" etc. Write facts as natural sentences or short notes.
|
||||
|
||||
@ -133,6 +139,15 @@ Output: {{"facts" : []}}
|
||||
Input: デバイスの電源を切って
|
||||
Output: {{"facts" : []}}
|
||||
|
||||
Input: ミュートボタンに不具合がある
|
||||
Output: {{"facts" : []}}
|
||||
|
||||
Input: コンシェルジュの電話番号を探している
|
||||
Output: {{"facts" : []}}
|
||||
|
||||
Input: DR1の照明状態を教えて
|
||||
Output: {{"facts" : []}}
|
||||
|
||||
Return the facts and preferences in a json format as shown above.
|
||||
|
||||
Remember the following:
|
||||
|
||||
Loading…
Reference in New Issue
Block a user