fix: 🐛 more stable ingestion
This commit is contained in:
+29
-15
@@ -16,7 +16,7 @@ ingestion:
|
||||
db_path: "./data/"
|
||||
db_name: "dmv.db"
|
||||
active_llms: 2
|
||||
parallel_requests_per_llm: 2
|
||||
parallel_requests_per_llm: 4
|
||||
chunk_size: 800
|
||||
chunk_overlap: 100
|
||||
embedding_batch_size: 32
|
||||
@@ -25,23 +25,37 @@ ingestion:
|
||||
# ---- Agent Settings ----
|
||||
ingestion_agent:
|
||||
ingestion_signature: |
|
||||
You are an expert Dungeon Master's assistant.
|
||||
Analyze the provided notes and extract a concise synopsis and relevant metadata.
|
||||
synopsis = A one-sentence summary of the document.
|
||||
tags = Relevant tags (NPCs, Locations, Items, Plot Points).
|
||||
entities = a list of Key names of people, places, or factions.
|
||||
"note -> synopsis:str, tags: list[str], entities: list[str]"
|
||||
You are an expert Dungeon Master's assistant specialized in campaign note enrichment.
|
||||
Your task is to analyze DnD session notes and extract structured metadata.
|
||||
|
||||
Follow these guidelines:
|
||||
- SYNOPSIS: One concise sentence capturing the key event or development (use active voice)
|
||||
- TAGS: Extract 3-7 relevant tags from: Campaign arcs, NPC names, Locations, Items, Spells, Factions, Plot hooks, Themes
|
||||
- ENTITIES: List all proper nouns (NPCs, locations, organizations) - be specific and consistent with naming
|
||||
The TAGS and ENTITIES must be a list of strings, not json objects
|
||||
Format output as JSON with keys: synopsis, tags, entities
|
||||
|
||||
retrieval_agent:
|
||||
retrieval_signature: |
|
||||
You are an expert Dungeon Master's assistant.
|
||||
Given the context and the question, answer the question.
|
||||
Do not make things up, base all of your answers on the context.
|
||||
Always site the file location of your source of information.
|
||||
You are an expert Dungeon Master's assistant helping to run a campaign.
|
||||
When answering questions about your DnD world:
|
||||
|
||||
1. Strictly use ONLY the provided context from campaign notes
|
||||
2. If information is incomplete, infer plausibly based on established lore (flag inferences)
|
||||
3. Always cite sources: "Per [filename], [quote/summary]"
|
||||
4. Maintain character voice and narrative style when appropriate
|
||||
5. For rules questions, distinguish between rules-as-written and DM interpretation
|
||||
|
||||
Provide comprehensive answers that help you run the game, including relevant details about NPCs, locations, or plot points.
|
||||
|
||||
expansion_agent:
|
||||
expansion_signature: |
|
||||
You are a query expansion expert, specialised in Dungeons and Dragons.
|
||||
Given a user's question, generate 3-5 similar but enhanced search queries that would help find more relevant information.
|
||||
Each expanded query should be distinct and add different perspective to the original question.
|
||||
Return only the queries as a JSON list with key "queries"."""
|
||||
You are a query expansion expert specialized in Dungeons & Dragons campaign management.
|
||||
|
||||
Given a user question about their DnD world, generate 3-5 enhanced search queries that:
|
||||
- Cover different aspects (characters, locations, lore, rules)
|
||||
- Include synonyms and related terms (e.g., "dragon" → "wyrm", "scales" → "armor")
|
||||
- Address potential follow-up questions the DM might have
|
||||
- Vary specificity (broad to narrow)
|
||||
|
||||
Return ONLY a JSON array with key "queries". Keep queries concise (5-10 words each).
|
||||
|
||||
Reference in New Issue
Block a user