Dataset Viewer
The dataset viewer is not available for this subset.
Cannot get the split names for the config 'default' of the dataset.
Exception:    SplitsNotFoundError
Message:      The split names could not be parsed from the dataset config.
Traceback:    Traceback (most recent call last):
                File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 286, in get_dataset_config_info
                  for split_generator in builder._split_generators(
                                         ~~~~~~~~~~~~~~~~~~~~~~~~~^
                      StreamingDownloadManager(base_path=builder.base_path, download_config=download_config)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                  )
                  ^
                File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/eval/eval.py", line 41, in _split_generators
                  first_examples = list(
                      islice(
                  ...<2 lines>...
                      )
                  )
                File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/eval/eval.py", line 60, in _iter_samples_from_log_files
                  sample_files.sort(key=self._sort_samples_key)
                  ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/eval/eval.py", line 56, in _sort_samples_key
                  return (int(epoch_idx_str), int(sample_idx_str))
                                              ~~~^^^^^^^^^^^^^^^^
              ValueError: invalid literal for int() with base 10: 'P01-amb__P01-neg'
              
              The above exception was the direct cause of the following exception:
              
              Traceback (most recent call last):
                File "/src/services/worker/src/worker/job_runners/config/split_names.py", line 68, in compute_split_names_from_streaming_response
                  for split in get_dataset_split_names(
                               ~~~~~~~~~~~~~~~~~~~~~~~^
                      path=dataset,
                      ^^^^^^^^^^^^^
                      config_name=config,
                      ^^^^^^^^^^^^^^^^^^^
                      token=hf_token,
                      ^^^^^^^^^^^^^^^
                  )
                  ^
                File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 340, in get_dataset_split_names
                  info = get_dataset_config_info(
                      path,
                  ...<6 lines>...
                      **config_kwargs,
                  )
                File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 291, in get_dataset_config_info
                  raise SplitsNotFoundError("The split names could not be parsed from the dataset config.") from err
              datasets.inspect.SplitsNotFoundError: The split names could not be parsed from the dataset config.

Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.

MMACI pilot v2 runs

Raw Inspect AI logs from the ten-case MMACI pilot on GPT-5.6 Sol, Gemini 3.1 Pro Preview, Kimi K3, and Qwen3.8 Max. episode/ contains the primary agentic evaluation; probing/ contains the secondary direct-judgment evaluation. Each directory contains four .eval logs plus Inspect's eval-set metadata. Open them with Inspect View or the Inspect Python API.

This is a hand-authored pilot for reviewing the task and harness, not a release benchmark or model leaderboard. Seven ambiguous cases run under both hidden answers and three determinate controls run once, giving 17 episode conditions per model. Each condition has one rollout. Before a model asks, paired hidden conditions have identical visible inputs, so differences between their no-ask trajectories are sampling variation rather than recognition of hidden state. Some episode rubrics and artifacts are still under review. Exact leak rates, completion rates, and model rankings should therefore be treated as descriptive.

The defensible preliminary observation is qualitative: frontier models often proceed despite decision-relevant conflicts, and their clarification behavior differs.

Downloads last month
32