Use a slightly smaller model. Reduce concurreny. Be more clear in the prompts

This commit is contained in:
William Jeynes
2026-04-02 20:10:57 +01:00
parent 7e586fe17d
commit 10f2644408
6 changed files with 10 additions and 21 deletions
+2 -2
View File
@@ -10,8 +10,8 @@ export function createModelNode(tools: any, promptPath: string): GraphNode<typeo
const sysPrompt = await hydratePrompt(promptPath, state); const sysPrompt = await hydratePrompt(promptPath, state);
const model = new ChatOllama({ const model = new ChatOllama({
model: "llama3.1:8b-instruct-fp16", model: "llama3.1:8b-instruct-q4_K_M",
temperature: 0.7, temperature: 0.3
}); });
const modelWithTools = model.bindTools(Object.values(tools)); const modelWithTools = model.bindTools(Object.values(tools));
+1 -1
View File
@@ -16,4 +16,4 @@ Relevent examples are included in preceeding messages, use these as exact inspir
The claim to normalize is: The claim to normalize is:
###TITLE### ###TITLE###
Produce no other text other than the condensed claim. Produce no other text other than the condensed claim in inverted commas. Nothing should be around the normalised claim.
-9
View File
@@ -1,9 +0,0 @@
Could the following real-world event:
###TECLAIM###
Be a trigger for the following disinformation:
###TITLE###
Respond with "RELATION", followed by : followed by a confidence score (VERYHIGH, HIGH, MEDIUM, LOW, VERYLOW) followed by : followed by the reason. Use no other words, just return the score and reason in format.
Ignore wether the event happened or not, purely consider the likiness of causation
+6
View File
@@ -17,6 +17,10 @@ Include a url to a source for your trigger event (not a web search, a specific u
Include the date that the event happened ("March 2022" for exmaple) Include the date that the event happened ("March 2022" for exmaple)
Use a JSON format with each entry containing "Event,ReasoningWhyRelevant,SearchQuery,Url,Date". Use a JSON format with each entry containing "Event,ReasoningWhyRelevant,SearchQuery,Url,Date".
Return ONLY valid JSON.
Do not include explanations.
Do not wrap in markdown.
Do not label where the json is using colons
Multiple tool invocations should be requested at once, if applicable. Multiple tool invocations should be requested at once, if applicable.
Use your abilities to look between the lines and produce some insightful analysis, thinking both short and long term. Use your abilities to look between the lines and produce some insightful analysis, thinking both short and long term.
@@ -26,4 +30,6 @@ Events will be reordered as part of processing, each statement must stand alone
The preceeding messages act as examples of previous responses to potentially ficitonal events and scores given. The preceeding messages act as examples of previous responses to potentially ficitonal events and scores given.
Analysis should only be completed for proposed events that would graner >0.7 points Analysis should only be completed for proposed events that would graner >0.7 points
Since URLs change frequently, use tools to retreive up to date informaiton everytime, provided examples or existing knowledge will be wrong or out of date.
Lets go through it step by step Lets go through it step by step
-8
View File
@@ -1,8 +0,0 @@
Do the search results cited below
###TESEARCH###
Support the idea that the following happened:
###TECLAIM###
Respond with "CONFIDENCE", followed by : followed by a confidence score (VERYHIGH, HIGH, MEDIUM, LOW, VERYLOW) followed by : followed by the reason. Use no other words, just return the score and reason in format.
Dates can be off by a few days, that would still be valid
+1 -1
View File
@@ -17,7 +17,7 @@ const AGENT_NAME = process.env.AGENT ?? "agent";
*/ */
const MODE = process.env.MODE ?? "claim"; const MODE = process.env.MODE ?? "claim";
const MAX_CONCURRENCY = 5; const MAX_CONCURRENCY = 1;
const client = new Client({ apiUrl: API_URL }); const client = new Client({ apiUrl: API_URL });