feat(i18n): add optional embedding model descriptions for multiple locales
Enhance the internationalization support by adding optional descriptions for the embedding model in English, Korean, Russian, and Chinese. Update the UI to reflect these changes, ensuring users are informed about the optional nature of the embedding model when configuring knowledge base settings.
This commit is contained in:
@@ -7,7 +7,7 @@ package agent
|
||||
// batch, when the KB still has no folders to anchor on). The result is applied
|
||||
// in reduce only to pages that don't already have a category, so user edits and
|
||||
// previously-filed pages are never churned.
|
||||
const WikiTaxonomyPlanPrompt = `You are organizing a wiki knowledge base into a navigation directory. Assign each item below to a directory path (category) so the whole set lands on ONE coherent tree that reuses existing folders.
|
||||
const WikiTaxonomyPlanPrompt = `You are organizing a wiki knowledge base into a navigation directory. Assign each item below to a directory path (category) so the whole set lands on ONE coherent tree.
|
||||
|
||||
<existing_folders>
|
||||
{{.ExistingTaxonomy}}
|
||||
@@ -20,12 +20,16 @@ const WikiTaxonomyPlanPrompt = `You are organizing a wiki knowledge base into a
|
||||
<instructions>
|
||||
For every item, output a category path: an array of folder labels from broad to narrow (at most 2 levels). The category classifies WHAT the item fundamentally IS (the stable library "shelf" it always sits on), never the role it plays in one document.
|
||||
|
||||
Rules:
|
||||
- Reuse the EXACT folder labels listed in <existing_folders> (character-for-character) whenever an item belongs under the same domain. Do NOT invent synonym folders (e.g. do NOT create "春节习俗" when "春节 / 传统习俗" already fits).
|
||||
How to choose a path for each item:
|
||||
1. If an existing folder in <existing_folders> fits, REUSE its EXACT label (character-for-character). Do NOT invent a synonym folder (e.g. do NOT create "春节习俗" when "春节 / 传统习俗" already fits).
|
||||
2. If NO existing folder fits, CREATE a new, broad, durable folder for it (e.g. an organization → "组织", a legal idea → "法律概念", a place → "地点"). The directory does not have to stay small — most items DO have a natural home, so coin a sensible top-level folder rather than leaving them unfiled. Group items of the SAME kind under the SAME new folder so the tree stays coherent.
|
||||
3. Only give an empty path [] when an item genuinely belongs to NO durable subject at all. This must be RARE. The absence of a matching existing folder is NOT a reason for []; create a folder instead.
|
||||
|
||||
Other rules:
|
||||
- Group items of the SAME kind under the SAME folder at the SAME depth. Do not file one equivalent item a level deeper than its siblings (e.g. avoid "地点 / 地址 / Address1" next to "地点 / Address2" — pick one consistent depth for equivalent items).
|
||||
- Prefer a single broad top-level folder; add a second level only for a genuinely durable sub-domain shared by several items.
|
||||
- Do NOT use the item type ("entity"/"concept") as a folder. Do NOT put slashes inside a single label.
|
||||
- Every item slug in <items> MUST appear exactly once in the output. If an item truly cannot be classified under any durable folder, give it an empty path [].
|
||||
- Every item slug in <items> MUST appear exactly once in the output.
|
||||
- Write ALL folder labels in {{.Language}}.
|
||||
|
||||
### JSON Formatting Rules
|
||||
|
||||
Reference in New Issue
Block a user