* refine prompt * small update * fix a small bug * remove debug config after execution * fix: only remove <think> at start * feat: support creating dataset & multi-eval frame (#1302) * feat: add iterative evolve and evaluation support with partial chain stop * feat: add FTDataEvaluator and support multiple implement functions in finetune * feat: data implement for pre-proposal and proposal and add datasets (#1303) * feat:(1) support for multi layer dataset extraction (2) add category.json for dataset in datasets/ * fix: fix bug for generate category.json * feat: add get_dataset_folder_desc * init data proposal and merge qzli/ft * update data proposal prompts and add max_position_embeddings and resolve confilcts * remove sample counts in data proposal * turn data and train to unified hypo_gen * refine prompts * remove category.json and add it to dataset_info * fix jinja problem and proposal done * lint * add ai-generated description and raw readme into dataset_info.json * update prompt for description * add datasets * initial fix for proposal of data * final version for data proposal * lint * feat: add stats in dataset_info, and enable data coder (#1306) * refactor(dataset): add stats into dataset_info.json, and remove dataset from gitignore_folder * feat: enable data coder and run data process * feat: Merge data coder (#1307) * feat: implement finetune data coding, evaluation, and config improvements * fix: deepspeed config path * fix: dataset info columns --------- Co-authored-by: Young <afe.young@gmail.com> * replace str length with token_limit * add readme to dataset_info and remove useless blank lines in scenario description * feat: dataset prepare * fix: extract prams script name * feat: add loss&predictions samples to feedback * remove duplicate envs and and add llm_api_preferences and enhance reasoning token limits * feat: network for ft_env * fix: remove gpt-4o, which has low quota * feat: a simple ui * feat: merge data and train task type (#1309) * feat: filter redundant prams of lf * fix: ui bug caused by removing task_type * fix: force agent to use high concurrency, and remove redundant prompt * feat: extract info from llama factory log, and check data exists before download * fix: add compatibility rules * feat: llm evaluator for data coder * feat: openai package in ft docker, and refine prompt * feat: refine ft ui, add more info * feat: add raw logs * refine data coder prompt(for feedback debug) * feat: select dataset in scen init * fix: ui for docker log seperately * feat: sync log through blob * improve ui, and add llm feedback in Runner&Exp2FB (#1312) * fix: ui bug to visualize docker log, and lint * feat: unified docker log for ft env, and some refactor * fix bugs and improve ui * feat: save log of evaluator(single feedback) * feat: add evaluator, set cleanup docker log * feat: call llm in RunnerEvaluator and Feedback * fix: extract structured error message in RunnerEvaluator * feat: feedback improve, and fix some bugs * feat: feedback improve when runner fails * small update * feat(UI): add running info and benchmark metric in loop expander * feat(UI): add render markdown toggle * feat: refine prompts and add error type in exp2fb * feat: add filterd params reason, set default benchmark timeout to infinite, and refine train loss express * recover dataset deepscaler * feat: set timeout in .env * refactor: unifiied ft_env timeout * feat: debug mode for data coder * feat: deliver data_stats after generate debug_data * feat: use gpt-5.1 as judge model, set judge_retry, and refine debug mode prompt * refine prompt * refactor: llama factory manager logic, and refine data processing prompt * feat(DockerEnv): support GPU selection via CUDA_VISIBLE_DEVICES * feat: set api concurrency via .env * fix: ft env timeout bug * feat: enable CondaEnv run * fix: can't update bin path in first run, and path bug in lf manager * feat(ui): set log path through .env * refactor(ui): wrap_lines, remove css * feat(coder): retry when parse code-block fail * fix: refine single-fb in ui, and fix path bug(not allow proposal to decide path) * fix: opencompass CondaEnv torch compatible with vllm * fix: refine error text in coding * feat: deepspeed config for CondaEnv * feat: memory estimator * fix: deepspeed package for condaenv * fix: use `client.chat.completions.create()` only * feat: flash attention for condaenv * feat: strong and weak models interface * fix: condaenv package dependency * use multi round conversation in llm finetune proposal * refine prompt for data processing * enable evolving in data coder * maximize output token size * fix: refine ui * fix: optional packages for llama factory * fix: torch denpendency for b200 * fix: opencompass dependency * update cot prompts * skip the sub implement * skip conda preparation if env exists * update chemcot datasets * fix: unify docker to use litellm * update readme and instructions * fix: set CUDA_VISIBLE_DEVICES for CondaEnv * feat: add panorama dataset, refactor dataset interface * feat: calculate token using tiktoken, and ndarray bug * fix: download subtasks of chemcotdataset seperately * feat: customized prepare func for datasets * feat: update new benchmarks * add datasets package * docs: readme for llm finetune * feat: download raw data directly, with post-process function * feat: analyze raw dataset * suppress litellm debug info * feat(ui): summary page * feat: run multi-jobs * feat: improve ui * feat: add path and checkout options to LLM finetune loop entrypoint * feat: add FinanceIQ_ppl benchmark with auto-download and dataset desc rendering * refactor: remove unused imports and dead code, fix session folder logging * feat: enable tablebench and tableInstruct dataset * refine dataset readme, and coder prompt * refine proposal and coder prompt * fix: ui path (default log path) * feat: add automatic LoRA model merging for benchmarking with vLLM * refactor: reorganize finetune benchmark and merge modules under benchmark dir * refactor: modularize benchmark config and error extraction for finetune scenario * fix: update benchmark import paths and disable env cache for device info * refactor docke&conda env and fix import bugs * modify init python file * feat: add FinanceIQ dataset split utility and integrate with pipeline * feat: set weak and strong model by env, distribute workload across models * feat: sample dataset and rm params for tensorboard, wandb * update script to run jobs * refine proposal prompt, remove specific dataset name * fix(ui): auto switch log folder * fix: estimate the processed full data after sample * feat: filter raw data more aggressively, and lower data_eval standard * feat: sync workspace to blob * feat: rdkit for chemcotbench * update qwen2.5&llama3.1 context * fix: force failure on validation error and remove try/except in validator * feat: unified error sample extraction (with test scripts) * feat: set conda cache with .env * feat: skip data eval if data pass in last evo * fix: rm redundant param * fix ui bug * refactor: centralize assign_code_list_to_evo in MultiProcessEvolvingStrategy * feat: add test_params.yaml generation and workspace cleanup improvements for finetune * refactor: replace get_clear_ws_cmd with clear_workspace and update prompts for hard check criteria * add bioprobench dataset * fix: handle commas in training config extraction and refactor prompt includes * bioprobench description * add bioprobench readme * feat: merge lora adapter for blackwell gpu * feat: support for multi benchmarks in one job * change dfficult aware content for training * update difficulty-aware and logging principles * fix: resolve variable name conflict in FTRunnerEvaluator * set job id accuracy to minute * feat(ui): display one selected metric per benchmark * feat: store sota exp, and fix ws_ckp bug * fix: truncate data.json in feedback * fix: opencompass data for conda env * fix: save only the last model * feat: set log path and ws path * fix: set overwrite_cache to avoid lock contention(through injecting params) * feat: redirect stdout to file in localenv * add pickle cache to dataset desc * fix CI * fix: remove redundant wrapper * feat: set python_unbuffered * move redirect stdout to env run * fix a small bug * move model folder * feat(ui): display benchmark baseline * fix: enrich scenario and benchmark description * fix: rewrite runner eval to accept easier * feat: compare with baseline when no SOTA * update tablebench readme * fix: switch back to single benchmark (for baseline) * feat(ui): add ws path in ui * refactor: update SOTA tracking to use DAG traversal and parent selection * fix: prioritize local_selection in trace and refactor sibling retrieval logic * refactor: unify error handling in feedback generation and update workspace injection * feat: add skip_loop_error_stepname to control error skip step in LoopBase * fix: set local_selection to NEW_ROOT for experiments without parent * feat: set different ports for jobs * feat: set different ports for jobs * feat: add upper data size limit for LLM fine-tuning and update related prompts * fix: replace get_truncated_stdout() with stdout for consistent output handling * refactor: remove data.json from cache and workspace logic, focus on script-based reuse * fix: rm target_scenario * feat: add selective cache extraction and custom cache key for data processing * fix(ui): bug when displaying tablebench * fix: filter config in dataset_info.json * feat: add test set, set valid set * feat(ui): update test score, and set color for final decision * feat: add test score for baseline and update ui * fix: use [-100:] as test range * feat: update data_stats in runner * feat: wait for opencompass init when run multi jobs * fix: adjust test&valid split * feat: force to generate COT(with <think> token), and add answer format in scenarios.json * feat: improve ui * fix: unify benchmark volume mounts and set extra_volumes for conda env * fix(ui): number color * fix: update GPU memory handling to use total memory in GB and streamline code * fix: set use_cot_postprocessor * feat: add env_dict to config classes and merge env vars in Env run * fix: let coder obey proposal * fix(ui): direction bug and update chemcot core metirc * fix: set consistent benchmark mount points and env vars for docker and conda * fix: addintional target for LoRA * feat: workspace dir log for benchmark running * fix: tableInstruct path bug and update benchmark description * feat: timeout for whole job * fix: align FinanceIQ import to opencompass * feat: use llm_judge for FinanceIQ * feat: switch to turn on <think> or not * feat: using scripts to redirect stdout, and run in different windows * feat: sync litellm log * fix: gpu memory format * fix: escape special characters in benchmark desc * fix: set data processing timeout to 1h * feat: set valid_loss and save_best_model * fix: inject timeout and stage * fix: loss history extract logic * feat: inject output dir * feat: inject eval batch size * feat: inject save_total_limit * feat: update data prompt * fix: escape shell special characters * fix: tablebench visualization UI * fix: move implementation validation to coder, and ignore injected params * feat: README for FinanceIQ dataset * fix: bioprobench desc error * fix: remove task alignment when coder eval * fix: FinanceIQ now extracts last capital as answer * fix: stdout contains binary data * feat: recover estimate full output and set eval setting automatically * fix(ui): precision for summary table * fix(ui): import error * feat: try to use lora * fix(api): fix litellm bug for code block * fix: refine prompts to give agent more decision space * chore(ci): fix mypy typing issues * chore(ci): format code with black * chore(ci): fix ruff lint violations * chore(ci): sort imports with isort * chore(ci): format code with black * test: temporarily skip extract_parameters imports due to numpy pin * fix: compatibility issues for qlib scenarios on finetune branch * fix(fin_factor): skip to fb for coder error * fix(loop): default skip to feedback step on skip_loop_error When skip_loop_error exception happens and skip_loop_error_stepname is not explicitly set, default to jumping to 'feedback' step if it exists, otherwise fall back to the last step (record). This prevents KeyError when record step tries to access feedback data that doesn't exist because we skipped the feedback phase. Also removed redundant skip_loop_error_stepname from finetune loop since it's now the default behavior. * add 'skip to record' to DS scenario like other scenarios * fix 2 scenarios bug about rd_loop class * fix: lint(mypy, ruff, black) error * fix: mypy lint error * fix data science scenario bug --------- Co-authored-by: Xu Yang <peteryang@vip.qq.com> Co-authored-by: Qizheng Li <jenssenlee@163.com> Co-authored-by: you-n-g <you-n-g@users.noreply.github.com> Co-authored-by: amstrongzyf <201840057@smail.nju.edu.cn> Co-authored-by: Young <afe.young@gmail.com> Co-authored-by: amstrongzyf <amstrongzyf@126.com> Co-authored-by: chelsea97 <zhuowbrown@gmail.com> Co-authored-by: SunsetWolf <Lv.Linlang@hotmail.com>
language, size_categories, license, configs
| language | size_categories | license | configs | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
mit |
|
TableBench: Table Question Answering Dataset
Dataset for TableBench: A Comprehensive and Complex Benchmark for Table Question Answering.
TableBench is a comprehensive and complex benchmark designed to evaluate Table Question Answering (TableQA) capabilities, covering 18 question categories across 4 major categories with 886 carefully curated test cases.
Overview
The TableBench dataset consists of two main components:
- TableBench (Test): 886 high-quality test cases for evaluation across 4 major reasoning categories
- TableInstruct (Train): Large-scale training dataset with diverse table QA examples
TableBench substantially pushes the boundaries of large language models in complex TableQA scenarios, aligning closely with the "Reasoning Complexity of Questions" dimension in real-world Table QA applications.
Task Categories
The benchmark covers 4 major categories with 18 sub-tasks:
-
Fact Checking: Verify factual statements against table data
- Simple fact verification, cross-table validation, temporal consistency
-
Numerical Reasoning: Mathematical computations and comparisons
- Arithmetic operations, aggregations, comparative analysis
-
Data Analysis: Complex analytical reasoning
- Impact analysis, correlation analysis, trend forecasting, statistical analysis
-
Visualization: Chart generation and interpretation
- Bar charts, line charts, pie charts, scatter plots
Data Sources
Test Data (TableBench):
- Repository: Multilingual-Multimodal-NLP/TableBench
- 886 carefully curated and verified test cases
- Enhanced version released April 2025 with error corrections
Train Data (TableInstruct):
- Repository: Multilingual-Multimodal-NLP/TableInstruct
- Large-scale instruction tuning dataset for table QA
- Diverse question types and reasoning patterns
Data Fields
The dataset contains the following key fields:
The TableInstruct dataset contains the following fields:
id(string): Unique identifier for each sampleqtype(string): Major task category (4 values)FactChecking,NumericalReasoning,DataAnalysis,Visualization
qsubtype(string): Specific sub-task type (18 values)- Examples:
Counting,Aggregation,Comparison,CorrelationAnalysis, etc.
- Examples:
instruction(string): Complete instruction template with task guidelines- Contains the full prompt template defining how to approach the task
- Includes role definition, guidelines, code format requirements
- Typically 800-15,000 characters depending on instruction type
instruction_type(string): Reasoning strategy type (4 values)DP(Direct Prompting),TCoT(Textual Chain-of-Thought)PoT(Program-of-Thought),SCoT(Structured Chain-of-Thought)
table(string): Table data in JSON format- Structure:
{"columns": [...], "data": [[...], [...], ...]}
- Structure:
question(string): Specific question about the tableresponse(string): Model's answer including reasoning process
TableBench Test Dataset Fields:
question: The table question or task descriptiontable: The table data (JSON format)answer: The ground truth answercategory: Major categorysubcategory: Specific sub-task type
Instruction Types and Reasoning Strategies
Tablebench training data (TableInstruct) supports multiple instruction types content that define how the model approaches reasoning and generates answers. Understanding these types is crucial for dataset filtering and fine-tuning strategy selection.
Available Instruction Type
1. Direct Prompting(DP) Characteristics:
- Provides solutions directly without intermediate reasoning steps
- Simplest instruction format focused on immediate answer generation
- Best for straightforward fact-checking and simple queries Instruction Template Pattern: You are a table analyst. Your task is to answer questions based on the table content. Read the table below in JSON format: [TABLE] Question: [QUESTION] Answer directly. Response Format: [Direct Answer]
2. Textual Chain-of-Thought (TCoT) Characteristics:
- LLMs incrementally derive intermediate steps through textual reasoning
- Natural language explanations for each reasoning step
- Suitable for complex reasoning requiring logical deduction
Instruction Template Pattern: You are a table analyst. Your task is to answer questions based on the table content. [Guidelines for step-by-step reasoning] Think step by step Show your reasoning process Provide the final answer *Response Format: Let's analyze this step by step: [First reasoning step] [Second reasoning step] ... Final Answer: [Answer]
3. Program-of-Thought (PoT)
Characteristics:
- Decomposes problems into executable Python code
- Separates computation from reasoning using programming
- Ideal for numerical reasoning and computational tasks
- Most common type in TableInstruct for analytical tasks
Instruction Template Pattern (actual from dataset): You are a data analyst proficient in Python. Your task is to write executable Python code to analyze the table and then answer questions. [Guidelines]
- Based on the question, write out your analytical approach, then write Python code
- The code needs to be concise and easy to understand
- Code blocks need to strictly start with ''' import pandas as pd df = pd.read_csv('table.csv') ... print(f'Final Answer: {answer}') ''' 4.Your analysis must be based entirely on the above data 5.Generate executable code with results using print function 6.Ensure to load the table with: df = pd.read_csv('table.csv')
4. Symbolic Chain-of-Thought (SCoT)
Characteristics:
- A methodology that utilizes Python-based instructions to facilitate logical reasoning
- Combines symbolic reasoning with executable code verification
- Three primary steps repeated until a definitive conclusion is derived
- Distinguishes itself from PoT by emphasizing iterative analysis-generation-simulation cycles
Three-Step Process:
- STEP-1: Analyzing the available information to determine the next move
- STEP-2: Generating instructions using Python programming language commands
- STEP-3: Simulating the outcomes by executing the instructions and analyzing the results
Instruction Template Pattern: You are a table analyst. Use symbolic reasoning with iterative Python commands. Process: STEP-1: Analyze available information to determine the next move STEP-2: Generate Python programming language commands STEP-3: Simulate outcomes by executing instructions and analyzing results Repeat these three steps until reaching a definitive conclusion
Evaluation Metrics
Different metrics are used based on task type:
| Task Type | Metric | Description |
|---|---|---|
| Fact Checking | Exact Match (EM) | Exact match of predicted statement |
| Numerical Reasoning | Exact Match (EM) | Correctness of numerical outputs |
| Impact Analysis | Exact Match (EM) | Precise match of influential factors |
| Correlation/Trend/Stats | EM_with_error_10 | ±10% numerical margin of error |
| Other Data Analysis | ROUGE-L | For open-ended textual responses |
| Visualization | Pass@1 | Correct chart generated on first attempt |
CoT Quality Assessment
IMPORTANT: Consider enhancing reasoning chains during training preparation.
| Dimension | Value |
|---|---|
| baseline_quality | medium-high |
| task_type | table_qa |
| polish_difficulty | medium |
Baseline: Training data (TableInstruct) contains reasoning examples, but test data focuses on final answers. For complex reasoning tasks (Data Analysis, Numerical Reasoning), generating detailed step-by-step CoT can significantly improve model performance.
Recommendation: For Data Analysis and Numerical Reasoning categories, expand reasoning chains to include:
- Table understanding and schema identification
- Step-by-step computation or logical reasoning
- Intermediate results and verification
- Final answer with confidence indicators
Example
Fact Checking
{
"question": "Based on the table, verify if the statement is true: 'Company A had higher revenue than Company B in Q4 2023'",
"table": "| Company | Q4 2023 Revenue |\n|---------|----------------|\n| A | $2.5M |\n| B | $3.1M |",
"answer": "False",
"category": "Fact Checking",
"subcategory": "simple_fact_verification"
}
Numerical Reasoning
{
"question": "What is the total revenue across all quarters for Product X?",
"table": "| Quarter | Product X Revenue |\n|---------|------------------|\n| Q1 | 150 |\n| Q2 | 200 |\n| Q3 | 175 |\n| Q4 | 225 |",
"answer": "750",
"category": "Numerical Reasoning",
"subcategory": "aggregation"
}
Data Analysis
{
"question": "Analyze the correlation between marketing spend and sales growth. What is the correlation coefficient?",
"table": "| Month | Marketing ($K) | Sales Growth (%) |\n|-------|----------------|------------------|\n| Jan | 50 | 12 |\n| Feb | 75 | 18 |\n| Mar | 60 | 15 |",
"answer": "0.95",
"category": "Data Analysis",
"subcategory": "correlation_analysis"
}
License
This dataset is released under the MIT License.