server-inference push halueval_qa
This commit is contained in:
56
config.json
Normal file
56
config.json
Normal file
@@ -0,0 +1,56 @@
|
||||
{
|
||||
"model": null,
|
||||
"signature": {
|
||||
"description": "Determine whether the answer to the question is hallucinated given the reference knowledge. As you reason, note any uncertainties, ambiguities, and gaps \u2014 both in how the instructions apply to the task at hand and in whether you have the knowledge needed to solve it. Be honest in your reasoning when you are unsure about your answer.",
|
||||
"properties": {
|
||||
"knowledge": {
|
||||
"__dspy_field_type": "input",
|
||||
"desc": "Reference knowledge used to verify the answer.",
|
||||
"prefix": "Knowledge:",
|
||||
"title": "Knowledge",
|
||||
"type": "string"
|
||||
},
|
||||
"question": {
|
||||
"__dspy_field_type": "input",
|
||||
"desc": "Question to answer using the reference knowledge.",
|
||||
"prefix": "Question:",
|
||||
"title": "Question",
|
||||
"type": "string"
|
||||
},
|
||||
"answer": {
|
||||
"__dspy_field_type": "input",
|
||||
"desc": "Answer to evaluate for hallucination.",
|
||||
"prefix": "Answer:",
|
||||
"title": "Answer",
|
||||
"type": "string"
|
||||
},
|
||||
"reasoning": {
|
||||
"__dspy_field_type": "output",
|
||||
"desc": "Step-by-step reasoning, including uncertainty, ambiguity, or uncertainty in your thought process when relevant.",
|
||||
"prefix": "Reasoning:",
|
||||
"title": "Reasoning",
|
||||
"type": "string"
|
||||
},
|
||||
"hallucination": {
|
||||
"__dspy_field_type": "output",
|
||||
"desc": "Final hallucination label: 'yes' if the answer is hallucinated, otherwise 'no'.",
|
||||
"enum": [
|
||||
"yes",
|
||||
"no"
|
||||
],
|
||||
"prefix": "Hallucination:",
|
||||
"title": "Hallucination",
|
||||
"type": "string"
|
||||
}
|
||||
},
|
||||
"required": [
|
||||
"knowledge",
|
||||
"question",
|
||||
"answer",
|
||||
"reasoning",
|
||||
"hallucination"
|
||||
],
|
||||
"title": "HaluEvalQaJudgeSig",
|
||||
"type": "object"
|
||||
}
|
||||
}
|
||||
Reference in New Issue
Block a user