xbb083 commited on
Commit
d846fa6
·
verified ·
1 Parent(s): a5cec24

Restore naturally ordered Foundational Analysis case paths

Browse files
This view is limited to 50 files because it contains too many changes.   See raw diff
Files changed (50) hide show
  1. foundational_analysis/cases/case10/case10_01.json +36 -0
  2. foundational_analysis/cases/case10/case10_02.json +36 -0
  3. foundational_analysis/cases/case10/case10_03.json +36 -0
  4. foundational_analysis/cases/case10/case10_04.json +36 -0
  5. foundational_analysis/cases/case10/case10_05.json +36 -0
  6. foundational_analysis/cases/case10/case10_06.json +36 -0
  7. foundational_analysis/cases/case10/case10_07.json +36 -0
  8. foundational_analysis/cases/case10/case10_08.json +36 -0
  9. foundational_analysis/cases/case10/case10_09.json +36 -0
  10. foundational_analysis/cases/case10/case10_10.json +36 -0
  11. foundational_analysis/cases/case10/case10_11.json +36 -0
  12. foundational_analysis/cases/case10/case10_12.json +36 -0
  13. foundational_analysis/cases/case10/case10_13.json +36 -0
  14. foundational_analysis/cases/case10/case10_14.json +36 -0
  15. foundational_analysis/cases/case10/case10_15.json +36 -0
  16. foundational_analysis/cases/case10/case10_16.json +36 -0
  17. foundational_analysis/cases/case10/case10_17.json +36 -0
  18. foundational_analysis/cases/case10/case10_18.json +36 -0
  19. foundational_analysis/cases/case10/case10_19.json +36 -0
  20. foundational_analysis/cases/case10/case10_20.json +36 -0
  21. foundational_analysis/cases/case10/case10_21.json +36 -0
  22. foundational_analysis/cases/case10/case10_22.json +36 -0
  23. foundational_analysis/cases/case10/case10_23.json +36 -0
  24. foundational_analysis/cases/case10/case10_24.json +36 -0
  25. foundational_analysis/cases/case10/case10_25.json +36 -0
  26. foundational_analysis/cases/case11/case11_01.json +35 -0
  27. foundational_analysis/cases/case11/case11_02.json +35 -0
  28. foundational_analysis/cases/case11/case11_03.json +35 -0
  29. foundational_analysis/cases/case11/case11_04.json +35 -0
  30. foundational_analysis/cases/case11/case11_05.json +35 -0
  31. foundational_analysis/cases/case11/case11_06.json +35 -0
  32. foundational_analysis/cases/case11/case11_07.json +35 -0
  33. foundational_analysis/cases/case11/case11_08.json +35 -0
  34. foundational_analysis/cases/case11/case11_09.json +35 -0
  35. foundational_analysis/cases/case11/case11_10.json +35 -0
  36. foundational_analysis/cases/case11/case11_11.json +35 -0
  37. foundational_analysis/cases/case11/case11_12.json +35 -0
  38. foundational_analysis/cases/case11/case11_13.json +35 -0
  39. foundational_analysis/cases/case11/case11_14.json +35 -0
  40. foundational_analysis/cases/case11/case11_15.json +35 -0
  41. foundational_analysis/cases/case11/case11_16.json +35 -0
  42. foundational_analysis/cases/case11/case11_17.json +35 -0
  43. foundational_analysis/cases/case11/case11_18.json +35 -0
  44. foundational_analysis/cases/case11/case11_19.json +35 -0
  45. foundational_analysis/cases/case11/case11_20.json +35 -0
  46. foundational_analysis/cases/case11/case11_21.json +35 -0
  47. foundational_analysis/cases/case11/case11_22.json +35 -0
  48. foundational_analysis/cases/case11/case11_23.json +35 -0
  49. foundational_analysis/cases/case11/case11_24.json +35 -0
  50. foundational_analysis/cases/case11/case11_25.json +35 -0
foundational_analysis/cases/case10/case10_01.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_01.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/ISRUC_01.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.306056,
22
+ "tolerance": 0.0153028
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "C4-F4"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_02.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_02.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/ISRUC_02.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.431466,
22
+ "tolerance": 0.021573300000000004
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "C4-F4"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_03.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_03.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/ISRUC_03.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.304628,
22
+ "tolerance": 0.0152314
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "C4-F4"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_04.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_04.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/ISRUC_04.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.291297,
22
+ "tolerance": 0.014564849999999999
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "C3-F3"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_05.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_05.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/ISRUC_05.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.354238,
22
+ "tolerance": 0.0177119
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "C3-F3"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_06.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "BCIC2020-3_01.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "BCIC2020-3"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/BCIC2020-3_01.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.466999,
22
+ "tolerance": 0.02334995
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "P3-P5"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_07.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "BCIC2020-3_02.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "BCIC2020-3"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/BCIC2020-3_02.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.334351,
22
+ "tolerance": 0.01671755
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "FC4-FC6"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_08.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "BCIC2020-3_03.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "BCIC2020-3"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/BCIC2020-3_03.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.446754,
22
+ "tolerance": 0.022337700000000002
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "AF7-F5"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_09.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "BCIC2020-3_04.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "BCIC2020-3"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/BCIC2020-3_04.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.514571,
22
+ "tolerance": 0.025728550000000003
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "F7-FT7"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_10.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "BCIC2020-3_05.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "BCIC2020-3"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/BCIC2020-3_05.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.490313,
22
+ "tolerance": 0.02451565
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "P1-P3"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_11.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SEED-V-01.cnt",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "SEED-V"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/SEED-V-01.cnt",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.352766,
22
+ "tolerance": 0.017638300000000003
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "PO6-PO8"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_12.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SEED-V-02.cnt",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "SEED-V"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/SEED-V-02.cnt",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.347057,
22
+ "tolerance": 0.01735285
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "PO3-PO5"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_13.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SEED-V-03.cnt",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "SEED-V"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/SEED-V-03.cnt",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.366734,
22
+ "tolerance": 0.0183367
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "P5-PO5"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_14.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SEED-V-04.cnt",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "SEED-V"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/SEED-V-04.cnt",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.474302,
22
+ "tolerance": 0.023715100000000003
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "O2-PO4"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_15.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SEED-V-05.cnt",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "SEED-V"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/SEED-V-05.cnt",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.42731,
22
+ "tolerance": 0.021365500000000003
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "P4-P6"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_16.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Mumtaz2016_01.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "Mumtaz2016"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/Mumtaz2016_01.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.368373,
22
+ "tolerance": 0.01841865
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "FP1-FP2"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_17.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Mumtaz2016_02.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "Mumtaz2016"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/Mumtaz2016_02.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.495031,
22
+ "tolerance": 0.02475155
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "F3-FP1"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_18.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Mumtaz2016_03.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "Mumtaz2016"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/Mumtaz2016_03.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.608099,
22
+ "tolerance": 0.03040495
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "F4-FZ"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_19.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Mumtaz2016_04.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "Mumtaz2016"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/Mumtaz2016_04.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.404867,
22
+ "tolerance": 0.02024335
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "FP1-FZ"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_20.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Mumtaz2016_05.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "Mumtaz2016"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/Mumtaz2016_05.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.479867,
22
+ "tolerance": 0.02399335
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "F3-FP1"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_21.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MentalArithmetic_01.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "MentalArithmetic"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/MentalArithmetic_01.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.463025,
22
+ "tolerance": 0.02315125
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "F4-FZ"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_22.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MentalArithmetic_02.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "MentalArithmetic"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/MentalArithmetic_02.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.577661,
22
+ "tolerance": 0.02888305
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "F7-FP1"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_23.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MentalArithmetic_03.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "MentalArithmetic"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/MentalArithmetic_03.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.478912,
22
+ "tolerance": 0.0239456
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "C4-CZ"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_24.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MentalArithmetic_04.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "MentalArithmetic"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/MentalArithmetic_04.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.551636,
22
+ "tolerance": 0.027581800000000004
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "F4-FZ"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case10/case10_25.json ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MentalArithmetic_05.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.5,
6
+ "original_dataset": "MentalArithmetic"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/MentalArithmetic_05.edf",
10
+ "instruction": "Please select EEG channels from the raw signal, apply an 8-13Hz alpha-band FIR (linear-phase) bandpass filter, and then use the first 30 seconds of the filtered signal to compute inter-channel correlations using the Pearson correlation coefficient. Then report: (1) the global synchronization value defined as the mean absolute correlation across all channel pairs, and (2) the single channel pair with the highest correlation coefficient."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) global synchronization value in alpha band\n2) highest-correlation channel pair\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"global_sync\" and \"top_pair\".\n5. \"global_sync\" must be a FLOAT.\n6. To extract \"top_pair\", first identify the two complete source channel labels. A referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. If the pair cannot be resolved into exactly two non-reference channels, set \"top_pair\" to null; do not guess. If global_sync is missing, set only global_sync to null.\n\n### OUTPUT TEMPLATE\n{\"global_sync\": <float|null>, \"top_pair\": <string|null>}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "alpha_global_sync_accuracy",
17
+ "type": "numeric_check",
18
+ "target_key": "global_sync",
19
+ "weight": 50,
20
+ "params": {
21
+ "gt_value": 0.479741,
22
+ "tolerance": 0.02398705
23
+ }
24
+ },
25
+ {
26
+ "metric_id": "highest_corr_pair_accuracy",
27
+ "type": "categorical_check",
28
+ "target_key": "top_pair",
29
+ "weight": 50,
30
+ "params": {
31
+ "gt_value": "F8-FP2"
32
+ }
33
+ }
34
+ ]
35
+ }
36
+ }
foundational_analysis/cases/case11/case11_01.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_01.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/ISRUC_01.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the 110-120 minute segment and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "delta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "theta"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_02.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_02.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/ISRUC_02.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the 110-120 minute segment and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "delta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "theta"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_03.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_03.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/ISRUC_03.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the 110-120 minute segment and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "delta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "alpha"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_04.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_04.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/ISRUC_04.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the 110-120 minute segment and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "delta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "theta"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_05.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "ISRUC_05.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "ISRUC"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/ISRUC_05.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the 110-120 minute segment and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "delta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "beta"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_06.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "BCIC2020-3_01.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "BCIC2020-3"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/BCIC2020-3_01.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "beta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "gamma"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_07.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "BCIC2020-3_02.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "BCIC2020-3"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/BCIC2020-3_02.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "beta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "gamma"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_08.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "BCIC2020-3_03.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "BCIC2020-3"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/BCIC2020-3_03.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "beta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "gamma"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_09.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "BCIC2020-3_04.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "BCIC2020-3"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/BCIC2020-3_04.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "beta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "gamma"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_10.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "BCIC2020-3_05.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "BCIC2020-3"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/BCIC2020-3_05.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "beta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "gamma"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_11.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SEED-V-01.cnt",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "SEED-V"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/SEED-V-01.cnt",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "delta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "beta"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_12.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SEED-V-02.cnt",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "SEED-V"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/SEED-V-02.cnt",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "delta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "theta"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_13.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SEED-V-03.cnt",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "SEED-V"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/SEED-V-03.cnt",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "delta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "theta"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_14.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SEED-V-04.cnt",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "SEED-V"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/SEED-V-04.cnt",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "delta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "beta"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_15.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "SEED-V-05.cnt",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "SEED-V"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/SEED-V-05.cnt",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "delta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "theta"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_16.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Mumtaz2016_01.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "Mumtaz2016"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/Mumtaz2016_01.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "delta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "alpha"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_17.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Mumtaz2016_02.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "Mumtaz2016"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/Mumtaz2016_02.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "delta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "alpha"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_18.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Mumtaz2016_03.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "Mumtaz2016"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/Mumtaz2016_03.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "alpha"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "delta"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_19.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Mumtaz2016_04.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "Mumtaz2016"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/Mumtaz2016_04.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "theta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "alpha"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_20.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "Mumtaz2016_05.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "Mumtaz2016"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/Mumtaz2016_05.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "alpha"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "theta"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_21.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MentalArithmetic_01.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "MentalArithmetic"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/MentalArithmetic_01.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "alpha"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "delta"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_22.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MentalArithmetic_02.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "MentalArithmetic"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/MentalArithmetic_02.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "delta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "alpha"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_23.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MentalArithmetic_03.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "MentalArithmetic"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/MentalArithmetic_03.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "delta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "alpha"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_24.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MentalArithmetic_04.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "MentalArithmetic"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/MentalArithmetic_04.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "alpha"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "delta"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }
foundational_analysis/cases/case11/case11_25.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "meta_info": {
3
+ "case_id": "MentalArithmetic_05.edf",
4
+ "bench_subset": "NeuroBench-Core",
5
+ "difficult": 1.0,
6
+ "original_dataset": "MentalArithmetic"
7
+ },
8
+ "agent_input": {
9
+ "data_path": "data/core/MentalArithmetic_05.edf",
10
+ "instruction": "Please determine the dominant and secondary dominant EEG frequency bands in the first 60 seconds and return two discrete band names. Return only band names chosen from: alpha, beta, delta, gamma, theta."
11
+ },
12
+ "eval_config": {
13
+ "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) dominant EEG band\n2) secondary dominant EEG band\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. Keys in JSON must be EXACTLY \"dominant_band\" and \"secondary_band\".\n5. Values must be lowercase strings and each must be one of: [alpha, beta, delta, gamma, theta].\n6. If one value is missing, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_band\": \u003cstring|null\u003e, \"secondary_band\": \u003cstring|null\u003e}",
14
+ "metrics": [
15
+ {
16
+ "metric_id": "dominant_band_accuracy",
17
+ "type": "categorical_check",
18
+ "target_key": "dominant_band",
19
+ "weight": 70,
20
+ "params": {
21
+ "gt_value": "delta"
22
+ }
23
+ },
24
+ {
25
+ "metric_id": "secondary_band_accuracy",
26
+ "type": "categorical_check",
27
+ "target_key": "secondary_band",
28
+ "weight": 30,
29
+ "params": {
30
+ "gt_value": "alpha"
31
+ }
32
+ }
33
+ ]
34
+ }
35
+ }