xbb083 commited on
Commit
bfff2d6
·
verified ·
1 Parent(s): ff24d20

Sync Sleep Assessment JSON cases from local

Browse files
This view is limited to 50 files because it contains too many changes.   See raw diff
Files changed (50) hide show
  1. sleep_assessment/cases/case1/case1_01.json +27 -0
  2. sleep_assessment/cases/case1/case1_02.json +27 -0
  3. sleep_assessment/cases/case1/case1_03.json +27 -0
  4. sleep_assessment/cases/case1/case1_04.json +27 -0
  5. sleep_assessment/cases/case1/case1_05.json +27 -0
  6. sleep_assessment/cases/case1/case1_06.json +27 -0
  7. sleep_assessment/cases/case1/case1_07.json +27 -0
  8. sleep_assessment/cases/case1/case1_08.json +27 -0
  9. sleep_assessment/cases/case1/case1_09.json +27 -0
  10. sleep_assessment/cases/case1/case1_10.json +27 -0
  11. sleep_assessment/cases/case1/case1_11.json +27 -0
  12. sleep_assessment/cases/case1/case1_12.json +27 -0
  13. sleep_assessment/cases/case1/case1_13.json +27 -0
  14. sleep_assessment/cases/case1/case1_14.json +27 -0
  15. sleep_assessment/cases/case1/case1_15.json +27 -0
  16. sleep_assessment/cases/case1/case1_16.json +27 -0
  17. sleep_assessment/cases/case1/case1_17.json +27 -0
  18. sleep_assessment/cases/case1/case1_18.json +27 -0
  19. sleep_assessment/cases/case1/case1_19.json +27 -0
  20. sleep_assessment/cases/case1/case1_20.json +27 -0
  21. sleep_assessment/cases/case1/case1_21.json +27 -0
  22. sleep_assessment/cases/case1/case1_22.json +27 -0
  23. sleep_assessment/cases/case1/case1_23.json +27 -0
  24. sleep_assessment/cases/case1/case1_24.json +27 -0
  25. sleep_assessment/cases/case1/case1_25.json +27 -0
  26. sleep_assessment/cases/case2/case2_01.json +44 -0
  27. sleep_assessment/cases/case2/case2_02.json +44 -0
  28. sleep_assessment/cases/case2/case2_03.json +44 -0
  29. sleep_assessment/cases/case2/case2_04.json +42 -0
  30. sleep_assessment/cases/case2/case2_05.json +42 -0
  31. sleep_assessment/cases/case2/case2_06.json +42 -0
  32. sleep_assessment/cases/case2/case2_07.json +40 -0
  33. sleep_assessment/cases/case2/case2_08.json +40 -0
  34. sleep_assessment/cases/case2/case2_09.json +40 -0
  35. sleep_assessment/cases/case2/case2_10.json +58 -0
  36. sleep_assessment/cases/case2/case2_11.json +58 -0
  37. sleep_assessment/cases/case2/case2_12.json +58 -0
  38. sleep_assessment/cases/case2/case2_13.json +44 -0
  39. sleep_assessment/cases/case2/case2_14.json +44 -0
  40. sleep_assessment/cases/case2/case2_15.json +44 -0
  41. sleep_assessment/cases/case3/case3_01.json +47 -0
  42. sleep_assessment/cases/case3/case3_02.json +47 -0
  43. sleep_assessment/cases/case3/case3_03.json +47 -0
  44. sleep_assessment/cases/case3/case3_04.json +47 -0
  45. sleep_assessment/cases/case3/case3_05.json +47 -0
  46. sleep_assessment/cases/case3/case3_06.json +47 -0
  47. sleep_assessment/cases/case3/case3_07.json +47 -0
  48. sleep_assessment/cases/case3/case3_08.json +47 -0
  49. sleep_assessment/cases/case3/case3_09.json +47 -0
  50. sleep_assessment/cases/case3/case3_10.json +47 -0
sleep_assessment/cases/case1/case1_01.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_01.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/ISRUC_01.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 5.5,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_02.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_02.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/ISRUC_02.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 55.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_03.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_03.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/ISRUC_03.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 3.5,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_04.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_04.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/ISRUC_04.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 1.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_05.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_05.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/ISRUC_05.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 75.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_06.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "HMC_01.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "HMC"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/HMC_01.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 4.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_07.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "HMC_02.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "HMC"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/HMC_02.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 3.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_08.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "HMC_03.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "HMC"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/HMC_03.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 1.5,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_09.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "HMC_04.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "HMC"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/HMC_04.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 3.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_10.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "HMC_05.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "HMC"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/HMC_05.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 22.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_11.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SHHS1_01.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "SHHS1"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/SHHS1_01.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 14.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_12.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SHHS1_02.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "SHHS1"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/SHHS1_02.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 0.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_13.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SHHS1_03.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "SHHS1"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/SHHS1_03.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 83.5,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_14.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SHHS1_04.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "SHHS1"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/SHHS1_04.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 41.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_15.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SHHS1_05.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "SHHS1"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/SHHS1_05.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 10.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_16.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MASSSS3_01.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "MASSSS3"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/MASSSS3_01.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 3.5,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_17.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MASSSS3_02.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "MASSSS3"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/MASSSS3_02.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 21.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_18.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MASSSS3_03.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "MASSSS3"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/MASSSS3_03.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 7.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_19.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MASSSS3_04.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "MASSSS3"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/MASSSS3_04.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 2.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_20.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MASSSS3_05.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "MASSSS3"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/MASSSS3_05.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 7.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_21.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Physionet2018_01.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "Physionet2018"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/Physionet2018_01.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 4.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_22.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Physionet2018_02.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "Physionet2018"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/Physionet2018_02.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 10.5,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_23.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Physionet2018_03.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "Physionet2018"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/Physionet2018_03.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 4.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_24.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Physionet2018_04.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "Physionet2018"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/Physionet2018_04.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 0.5,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case1/case1_25.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Physionet2018_05.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "Physionet2018"
7
+ },
8
+ "agent_input": {
9
+ "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.",
10
+ "label_path": "data/sleep/Physionet2018_05.npy"
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": <float>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "sleep_onset_latency_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "sleep_onset_latency_min",
19
+ "weight": 100,
20
+ "params": {
21
+ "gt_value": 1.0,
22
+ "tolerance": 2.0
23
+ }
24
+ }
25
+ ]
26
+ }
27
+ }
sleep_assessment/cases/case2/case2_01.json ADDED
@@ -0,0 +1,44 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_01.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/sleep/ISRUC_01.edf",
10
+ "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": <integer|null>, \"eeg_channels\": <array|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "channel_count_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "channel_count",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 19,
22
+ "tolerance": 0.1
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "eeg_channel_set_match",
27
+ "type": "set_match_check",
28
+ "target_key": "eeg_channels",
29
+ "weight": 70,
30
+ "params": {
31
+ "gt_value": [
32
+ "F3-A2",
33
+ "C3-A2",
34
+ "O1-A2",
35
+ "F4-A1",
36
+ "C4-A1",
37
+ "O2-A1"
38
+ ],
39
+ "match_mode": "exact"
40
+ }
41
+ }
42
+ ]
43
+ }
44
+ }
sleep_assessment/cases/case2/case2_02.json ADDED
@@ -0,0 +1,44 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_02.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/sleep/ISRUC_02.edf",
10
+ "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": <integer|null>, \"eeg_channels\": <array|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "channel_count_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "channel_count",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 19,
22
+ "tolerance": 0.1
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "eeg_channel_set_match",
27
+ "type": "set_match_check",
28
+ "target_key": "eeg_channels",
29
+ "weight": 70,
30
+ "params": {
31
+ "gt_value": [
32
+ "F3-A2",
33
+ "C3-A2",
34
+ "O1-A2",
35
+ "F4-A1",
36
+ "C4-A1",
37
+ "O2-A1"
38
+ ],
39
+ "match_mode": "exact"
40
+ }
41
+ }
42
+ ]
43
+ }
44
+ }
sleep_assessment/cases/case2/case2_03.json ADDED
@@ -0,0 +1,44 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_03.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/sleep/ISRUC_03.edf",
10
+ "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": <integer|null>, \"eeg_channels\": <array|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "channel_count_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "channel_count",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 19,
22
+ "tolerance": 0.1
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "eeg_channel_set_match",
27
+ "type": "set_match_check",
28
+ "target_key": "eeg_channels",
29
+ "weight": 70,
30
+ "params": {
31
+ "gt_value": [
32
+ "F3-A2",
33
+ "C3-A2",
34
+ "O1-A2",
35
+ "F4-A1",
36
+ "C4-A1",
37
+ "O2-A1"
38
+ ],
39
+ "match_mode": "exact"
40
+ }
41
+ }
42
+ ]
43
+ }
44
+ }
sleep_assessment/cases/case2/case2_04.json ADDED
@@ -0,0 +1,42 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "HMC_01.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "HMC"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/sleep/HMC_01.edf",
10
+ "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": <integer|null>, \"eeg_channels\": <array|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "channel_count_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "channel_count",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 8,
22
+ "tolerance": 0.1
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "eeg_channel_set_match",
27
+ "type": "set_match_check",
28
+ "target_key": "eeg_channels",
29
+ "weight": 70,
30
+ "params": {
31
+ "gt_value": [
32
+ "EEG F4-M1",
33
+ "EEG C4-M1",
34
+ "EEG O2-M1",
35
+ "EEG C3-M2"
36
+ ],
37
+ "match_mode": "exact"
38
+ }
39
+ }
40
+ ]
41
+ }
42
+ }
sleep_assessment/cases/case2/case2_05.json ADDED
@@ -0,0 +1,42 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "HMC_02.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "HMC"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/sleep/HMC_02.edf",
10
+ "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": <integer|null>, \"eeg_channels\": <array|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "channel_count_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "channel_count",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 8,
22
+ "tolerance": 0.1
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "eeg_channel_set_match",
27
+ "type": "set_match_check",
28
+ "target_key": "eeg_channels",
29
+ "weight": 70,
30
+ "params": {
31
+ "gt_value": [
32
+ "EEG F4-M1",
33
+ "EEG C4-M1",
34
+ "EEG O2-M1",
35
+ "EEG C3-M2"
36
+ ],
37
+ "match_mode": "exact"
38
+ }
39
+ }
40
+ ]
41
+ }
42
+ }
sleep_assessment/cases/case2/case2_06.json ADDED
@@ -0,0 +1,42 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "HMC_03.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "HMC"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/sleep/HMC_03.edf",
10
+ "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": <integer|null>, \"eeg_channels\": <array|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "channel_count_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "channel_count",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 8,
22
+ "tolerance": 0.1
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "eeg_channel_set_match",
27
+ "type": "set_match_check",
28
+ "target_key": "eeg_channels",
29
+ "weight": 70,
30
+ "params": {
31
+ "gt_value": [
32
+ "EEG F4-M1",
33
+ "EEG C4-M1",
34
+ "EEG O2-M1",
35
+ "EEG C3-M2"
36
+ ],
37
+ "match_mode": "exact"
38
+ }
39
+ }
40
+ ]
41
+ }
42
+ }
sleep_assessment/cases/case2/case2_07.json ADDED
@@ -0,0 +1,40 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SHHS1_01.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "SHHS1"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/sleep/SHHS1_01.edf",
10
+ "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": <integer|null>, \"eeg_channels\": <array|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "channel_count_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "channel_count",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 14,
22
+ "tolerance": 0.1
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "eeg_channel_set_match",
27
+ "type": "set_match_check",
28
+ "target_key": "eeg_channels",
29
+ "weight": 70,
30
+ "params": {
31
+ "gt_value": [
32
+ "EEG(sec)",
33
+ "EEG"
34
+ ],
35
+ "match_mode": "exact"
36
+ }
37
+ }
38
+ ]
39
+ }
40
+ }
sleep_assessment/cases/case2/case2_08.json ADDED
@@ -0,0 +1,40 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SHHS1_02.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "SHHS1"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/sleep/SHHS1_02.edf",
10
+ "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": <integer|null>, \"eeg_channels\": <array|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "channel_count_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "channel_count",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 14,
22
+ "tolerance": 0.1
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "eeg_channel_set_match",
27
+ "type": "set_match_check",
28
+ "target_key": "eeg_channels",
29
+ "weight": 70,
30
+ "params": {
31
+ "gt_value": [
32
+ "EEG(sec)",
33
+ "EEG"
34
+ ],
35
+ "match_mode": "exact"
36
+ }
37
+ }
38
+ ]
39
+ }
40
+ }
sleep_assessment/cases/case2/case2_09.json ADDED
@@ -0,0 +1,40 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SHHS1_03.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "SHHS1"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/sleep/SHHS1_03.edf",
10
+ "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": <integer|null>, \"eeg_channels\": <array|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "channel_count_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "channel_count",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 14,
22
+ "tolerance": 0.1
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "eeg_channel_set_match",
27
+ "type": "set_match_check",
28
+ "target_key": "eeg_channels",
29
+ "weight": 70,
30
+ "params": {
31
+ "gt_value": [
32
+ "EEG(sec)",
33
+ "EEG"
34
+ ],
35
+ "match_mode": "exact"
36
+ }
37
+ }
38
+ ]
39
+ }
40
+ }
sleep_assessment/cases/case2/case2_10.json ADDED
@@ -0,0 +1,58 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MASSSS3_01.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "MASSSS3"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/sleep/MASSSS3_01.edf",
10
+ "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": <integer|null>, \"eeg_channels\": <array|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "channel_count_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "channel_count",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 27,
22
+ "tolerance": 0.1
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "eeg_channel_set_match",
27
+ "type": "set_match_check",
28
+ "target_key": "eeg_channels",
29
+ "weight": 70,
30
+ "params": {
31
+ "gt_value": [
32
+ "EEG Fp1-LER",
33
+ "EEG Fp2-LER",
34
+ "EEG F7-LER",
35
+ "EEG F8-LER",
36
+ "EEG F3-LER",
37
+ "EEG F4-LER",
38
+ "EEG T3-LER",
39
+ "EEG T4-LER",
40
+ "EEG C3-LER",
41
+ "EEG C4-LER",
42
+ "EEG T5-LER",
43
+ "EEG T6-LER",
44
+ "EEG P3-LER",
45
+ "EEG P4-LER",
46
+ "EEG O1-LER",
47
+ "EEG O2-LER",
48
+ "EEG Fz-LER",
49
+ "EEG Cz-LER",
50
+ "EEG Pz-LER",
51
+ "EEG Oz-LER"
52
+ ],
53
+ "match_mode": "exact"
54
+ }
55
+ }
56
+ ]
57
+ }
58
+ }
sleep_assessment/cases/case2/case2_11.json ADDED
@@ -0,0 +1,58 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MASSSS3_02.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "MASSSS3"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/sleep/MASSSS3_02.edf",
10
+ "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": <integer|null>, \"eeg_channels\": <array|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "channel_count_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "channel_count",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 27,
22
+ "tolerance": 0.1
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "eeg_channel_set_match",
27
+ "type": "set_match_check",
28
+ "target_key": "eeg_channels",
29
+ "weight": 70,
30
+ "params": {
31
+ "gt_value": [
32
+ "EEG Fp1-LER",
33
+ "EEG Fp2-LER",
34
+ "EEG F7-LER",
35
+ "EEG F8-LER",
36
+ "EEG F3-LER",
37
+ "EEG F4-LER",
38
+ "EEG T3-LER",
39
+ "EEG T4-LER",
40
+ "EEG C3-LER",
41
+ "EEG C4-LER",
42
+ "EEG T5-LER",
43
+ "EEG T6-LER",
44
+ "EEG P3-LER",
45
+ "EEG P4-LER",
46
+ "EEG O1-LER",
47
+ "EEG O2-LER",
48
+ "EEG Fz-LER",
49
+ "EEG Cz-LER",
50
+ "EEG Pz-LER",
51
+ "EEG Oz-LER"
52
+ ],
53
+ "match_mode": "exact"
54
+ }
55
+ }
56
+ ]
57
+ }
58
+ }
sleep_assessment/cases/case2/case2_12.json ADDED
@@ -0,0 +1,58 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MASSSS3_03.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "MASSSS3"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/sleep/MASSSS3_03.edf",
10
+ "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": <integer|null>, \"eeg_channels\": <array|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "channel_count_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "channel_count",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 27,
22
+ "tolerance": 0.1
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "eeg_channel_set_match",
27
+ "type": "set_match_check",
28
+ "target_key": "eeg_channels",
29
+ "weight": 70,
30
+ "params": {
31
+ "gt_value": [
32
+ "EEG Fp1-LER",
33
+ "EEG Fp2-LER",
34
+ "EEG F7-LER",
35
+ "EEG F8-LER",
36
+ "EEG F3-LER",
37
+ "EEG F4-LER",
38
+ "EEG T3-LER",
39
+ "EEG T4-LER",
40
+ "EEG C3-LER",
41
+ "EEG C4-LER",
42
+ "EEG T5-LER",
43
+ "EEG T6-LER",
44
+ "EEG P3-LER",
45
+ "EEG P4-LER",
46
+ "EEG O1-LER",
47
+ "EEG O2-LER",
48
+ "EEG Fz-LER",
49
+ "EEG Cz-LER",
50
+ "EEG Pz-LER",
51
+ "EEG Oz-LER"
52
+ ],
53
+ "match_mode": "exact"
54
+ }
55
+ }
56
+ ]
57
+ }
58
+ }
sleep_assessment/cases/case2/case2_13.json ADDED
@@ -0,0 +1,44 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Physionet2018_01.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "Physionet2018"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/sleep/Physionet2018_01.edf",
10
+ "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": <integer|null>, \"eeg_channels\": <array|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "channel_count_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "channel_count",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 13,
22
+ "tolerance": 0.1
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "eeg_channel_set_match",
27
+ "type": "set_match_check",
28
+ "target_key": "eeg_channels",
29
+ "weight": 70,
30
+ "params": {
31
+ "gt_value": [
32
+ "F3-M2",
33
+ "F4-M1",
34
+ "C3-M2",
35
+ "C4-M1",
36
+ "O1-M2",
37
+ "O2-M1"
38
+ ],
39
+ "match_mode": "exact"
40
+ }
41
+ }
42
+ ]
43
+ }
44
+ }
sleep_assessment/cases/case2/case2_14.json ADDED
@@ -0,0 +1,44 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Physionet2018_02.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "Physionet2018"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/sleep/Physionet2018_02.edf",
10
+ "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": <integer|null>, \"eeg_channels\": <array|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "channel_count_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "channel_count",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 13,
22
+ "tolerance": 0.1
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "eeg_channel_set_match",
27
+ "type": "set_match_check",
28
+ "target_key": "eeg_channels",
29
+ "weight": 70,
30
+ "params": {
31
+ "gt_value": [
32
+ "F3-M2",
33
+ "F4-M1",
34
+ "C3-M2",
35
+ "C4-M1",
36
+ "O1-M2",
37
+ "O2-M1"
38
+ ],
39
+ "match_mode": "exact"
40
+ }
41
+ }
42
+ ]
43
+ }
44
+ }
sleep_assessment/cases/case2/case2_15.json ADDED
@@ -0,0 +1,44 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Physionet2018_03.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "Physionet2018"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/sleep/Physionet2018_03.edf",
10
+ "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": <integer|null>, \"eeg_channels\": <array|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "channel_count_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "channel_count",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 13,
22
+ "tolerance": 0.1
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "eeg_channel_set_match",
27
+ "type": "set_match_check",
28
+ "target_key": "eeg_channels",
29
+ "weight": 70,
30
+ "params": {
31
+ "gt_value": [
32
+ "F3-M2",
33
+ "F4-M1",
34
+ "C3-M2",
35
+ "C4-M1",
36
+ "O1-M2",
37
+ "O2-M1"
38
+ ],
39
+ "match_mode": "exact"
40
+ }
41
+ }
42
+ ]
43
+ }
44
+ }
sleep_assessment/cases/case3/case3_01.json ADDED
@@ -0,0 +1,47 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_01.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "label_path": "data/sleep/ISRUC_01.npy",
10
+ "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": <float|null>, \"tib_min\": <float|null>, \"se_percent\": <float|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "tst_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "tst_min",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 308.0,
22
+ "tolerance": 9.24
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "tib_accuracy",
27
+ "type": "numeric_check",
28
+ "target_key": "tib_min",
29
+ "weight": 30,
30
+ "params": {
31
+ "gt_value": 440.0,
32
+ "tolerance": 13.2
33
+ }
34
+ },
35
+ {
36
+ "metric_id": "se_accuracy",
37
+ "type": "numeric_check",
38
+ "target_key": "se_percent",
39
+ "weight": 40,
40
+ "params": {
41
+ "gt_value": 70.0,
42
+ "tolerance": 2.1
43
+ }
44
+ }
45
+ ]
46
+ }
47
+ }
sleep_assessment/cases/case3/case3_02.json ADDED
@@ -0,0 +1,47 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_02.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "label_path": "data/sleep/ISRUC_02.npy",
10
+ "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": <float|null>, \"tib_min\": <float|null>, \"se_percent\": <float|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "tst_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "tst_min",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 359.5,
22
+ "tolerance": 10.785
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "tib_accuracy",
27
+ "type": "numeric_check",
28
+ "target_key": "tib_min",
29
+ "weight": 30,
30
+ "params": {
31
+ "gt_value": 482.0,
32
+ "tolerance": 14.459999999999999
33
+ }
34
+ },
35
+ {
36
+ "metric_id": "se_accuracy",
37
+ "type": "numeric_check",
38
+ "target_key": "se_percent",
39
+ "weight": 40,
40
+ "params": {
41
+ "gt_value": 74.5850622406639,
42
+ "tolerance": 2.237551867219917
43
+ }
44
+ }
45
+ ]
46
+ }
47
+ }
sleep_assessment/cases/case3/case3_03.json ADDED
@@ -0,0 +1,47 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_03.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "label_path": "data/sleep/ISRUC_03.npy",
10
+ "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": <float|null>, \"tib_min\": <float|null>, \"se_percent\": <float|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "tst_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "tst_min",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 405.5,
22
+ "tolerance": 12.165
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "tib_accuracy",
27
+ "type": "numeric_check",
28
+ "target_key": "tib_min",
29
+ "weight": 30,
30
+ "params": {
31
+ "gt_value": 471.5,
32
+ "tolerance": 14.145
33
+ }
34
+ },
35
+ {
36
+ "metric_id": "se_accuracy",
37
+ "type": "numeric_check",
38
+ "target_key": "se_percent",
39
+ "weight": 40,
40
+ "params": {
41
+ "gt_value": 86.00212089077412,
42
+ "tolerance": 2.5800636267232235
43
+ }
44
+ }
45
+ ]
46
+ }
47
+ }
sleep_assessment/cases/case3/case3_04.json ADDED
@@ -0,0 +1,47 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_04.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "label_path": "data/sleep/ISRUC_04.npy",
10
+ "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": <float|null>, \"tib_min\": <float|null>, \"se_percent\": <float|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "tst_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "tst_min",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 467.5,
22
+ "tolerance": 14.025
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "tib_accuracy",
27
+ "type": "numeric_check",
28
+ "target_key": "tib_min",
29
+ "weight": 30,
30
+ "params": {
31
+ "gt_value": 481.5,
32
+ "tolerance": 14.445
33
+ }
34
+ },
35
+ {
36
+ "metric_id": "se_accuracy",
37
+ "type": "numeric_check",
38
+ "target_key": "se_percent",
39
+ "weight": 40,
40
+ "params": {
41
+ "gt_value": 97.09241952232607,
42
+ "tolerance": 2.912772585669782
43
+ }
44
+ }
45
+ ]
46
+ }
47
+ }
sleep_assessment/cases/case3/case3_05.json ADDED
@@ -0,0 +1,47 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_05.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "label_path": "data/sleep/ISRUC_05.npy",
10
+ "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": <float|null>, \"tib_min\": <float|null>, \"se_percent\": <float|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "tst_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "tst_min",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 289.5,
22
+ "tolerance": 8.685
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "tib_accuracy",
27
+ "type": "numeric_check",
28
+ "target_key": "tib_min",
29
+ "weight": 30,
30
+ "params": {
31
+ "gt_value": 437.5,
32
+ "tolerance": 13.125
33
+ }
34
+ },
35
+ {
36
+ "metric_id": "se_accuracy",
37
+ "type": "numeric_check",
38
+ "target_key": "se_percent",
39
+ "weight": 40,
40
+ "params": {
41
+ "gt_value": 66.17142857142856,
42
+ "tolerance": 1.9851428571428569
43
+ }
44
+ }
45
+ ]
46
+ }
47
+ }
sleep_assessment/cases/case3/case3_06.json ADDED
@@ -0,0 +1,47 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "HMC_01.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "HMC"
7
+ },
8
+ "agent_input": {
9
+ "label_path": "data/sleep/HMC_01.npy",
10
+ "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": <float|null>, \"tib_min\": <float|null>, \"se_percent\": <float|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "tst_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "tst_min",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 351.5,
22
+ "tolerance": 10.545
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "tib_accuracy",
27
+ "type": "numeric_check",
28
+ "target_key": "tib_min",
29
+ "weight": 30,
30
+ "params": {
31
+ "gt_value": 427.0,
32
+ "tolerance": 12.809999999999999
33
+ }
34
+ },
35
+ {
36
+ "metric_id": "se_accuracy",
37
+ "type": "numeric_check",
38
+ "target_key": "se_percent",
39
+ "weight": 40,
40
+ "params": {
41
+ "gt_value": 82.31850117096019,
42
+ "tolerance": 2.469555035128806
43
+ }
44
+ }
45
+ ]
46
+ }
47
+ }
sleep_assessment/cases/case3/case3_07.json ADDED
@@ -0,0 +1,47 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "HMC_02.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "HMC"
7
+ },
8
+ "agent_input": {
9
+ "label_path": "data/sleep/HMC_02.npy",
10
+ "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": <float|null>, \"tib_min\": <float|null>, \"se_percent\": <float|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "tst_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "tst_min",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 387.0,
22
+ "tolerance": 11.61
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "tib_accuracy",
27
+ "type": "numeric_check",
28
+ "target_key": "tib_min",
29
+ "weight": 30,
30
+ "params": {
31
+ "gt_value": 428.0,
32
+ "tolerance": 12.84
33
+ }
34
+ },
35
+ {
36
+ "metric_id": "se_accuracy",
37
+ "type": "numeric_check",
38
+ "target_key": "se_percent",
39
+ "weight": 40,
40
+ "params": {
41
+ "gt_value": 90.42056074766354,
42
+ "tolerance": 2.712616822429906
43
+ }
44
+ }
45
+ ]
46
+ }
47
+ }
sleep_assessment/cases/case3/case3_08.json ADDED
@@ -0,0 +1,47 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "HMC_03.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "HMC"
7
+ },
8
+ "agent_input": {
9
+ "label_path": "data/sleep/HMC_03.npy",
10
+ "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": <float|null>, \"tib_min\": <float|null>, \"se_percent\": <float|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "tst_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "tst_min",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 275.5,
22
+ "tolerance": 8.265
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "tib_accuracy",
27
+ "type": "numeric_check",
28
+ "target_key": "tib_min",
29
+ "weight": 30,
30
+ "params": {
31
+ "gt_value": 477.0,
32
+ "tolerance": 14.309999999999999
33
+ }
34
+ },
35
+ {
36
+ "metric_id": "se_accuracy",
37
+ "type": "numeric_check",
38
+ "target_key": "se_percent",
39
+ "weight": 40,
40
+ "params": {
41
+ "gt_value": 57.75681341719078,
42
+ "tolerance": 1.7327044025157232
43
+ }
44
+ }
45
+ ]
46
+ }
47
+ }
sleep_assessment/cases/case3/case3_09.json ADDED
@@ -0,0 +1,47 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "HMC_04.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "HMC"
7
+ },
8
+ "agent_input": {
9
+ "label_path": "data/sleep/HMC_04.npy",
10
+ "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": <float|null>, \"tib_min\": <float|null>, \"se_percent\": <float|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "tst_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "tst_min",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 468.0,
22
+ "tolerance": 14.04
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "tib_accuracy",
27
+ "type": "numeric_check",
28
+ "target_key": "tib_min",
29
+ "weight": 30,
30
+ "params": {
31
+ "gt_value": 508.0,
32
+ "tolerance": 15.24
33
+ }
34
+ },
35
+ {
36
+ "metric_id": "se_accuracy",
37
+ "type": "numeric_check",
38
+ "target_key": "se_percent",
39
+ "weight": 40,
40
+ "params": {
41
+ "gt_value": 92.1259842519685,
42
+ "tolerance": 2.763779527559055
43
+ }
44
+ }
45
+ ]
46
+ }
47
+ }
sleep_assessment/cases/case3/case3_10.json ADDED
@@ -0,0 +1,47 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "HMC_05.edf",
4
+ "bench_subset": "NeuroBench-Sleep",
5
+ "difficult": 1,
6
+ "original_dataset": "HMC"
7
+ },
8
+ "agent_input": {
9
+ "label_path": "data/sleep/HMC_05.npy",
10
+ "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": <float|null>, \"tib_min\": <float|null>, \"se_percent\": <float|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "tst_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "tst_min",
19
+ "weight": 30,
20
+ "params": {
21
+ "gt_value": 379.0,
22
+ "tolerance": 11.37
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "tib_accuracy",
27
+ "type": "numeric_check",
28
+ "target_key": "tib_min",
29
+ "weight": 30,
30
+ "params": {
31
+ "gt_value": 479.5,
32
+ "tolerance": 14.385
33
+ }
34
+ },
35
+ {
36
+ "metric_id": "se_accuracy",
37
+ "type": "numeric_check",
38
+ "target_key": "se_percent",
39
+ "weight": 40,
40
+ "params": {
41
+ "gt_value": 79.04066736183525,
42
+ "tolerance": 2.3712200208550573
43
+ }
44
+ }
45
+ ]
46
+ }
47
+ }