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/harbor/harbor.py", line 171, in _split_generators
                  raise DataFilesNotFoundError("No task.toml or instruction.md files found")
              datasets.exceptions.DataFilesNotFoundError: No task.toml or instruction.md files found
              
              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.

Vivameda synthetic intelligence samples

15 fictional question-and-answer examples for developers exploring company intelligence and historical reasoning in agent workflows. Version 3, 10 October 2026.

Every row is synthetic and manually authored for this showcase. These are illustrations of reasoning boundaries, not outputs from the production engine, a benchmark, a training recommendation, or evidence of model performance. No proprietary panel or provider records were used to create these examples.

Additional reading

  • Exelixis case study: real company, retained historical analysis and public filings; explicitly qualified, not a forecast or synthetic example.
  • MCP integration example: illustrative staged engineering interface; no live client access announced.

The case study is separate from the synthetic dataset rows. No native panel rows or person-level records are provided.

Sample sets

Use case Examples Purpose
Strategy reasoning 5 Separate structural observations, hypotheses and business conclusions
Company comparison 4 Examine comparability, coverage and historical peer selection
Reference forecasting 4 Explain reference classes, horizons and limits of transfer
Diligence 2 Separate missing observations and corporate-event evidence

All sets are in samples.jsonl; filter on use_case. The original three examples remain unchanged.

Fields

sample_id is a stable fictional identifier. synthetic is always true. company is explicitly fictional. question and answer illustrate an analysis interaction. reference_sample_size and outcome_rate are always null: this release supplies no numerical forecast or reference calculation. limitations states the evidence boundary.

Example

Question: Can one named analog establish a base rate?

Illustrative answer: No. One analog is a case illustration, not a population estimate. Separate analog narratives from aggregate reference rates and disclose how comparators were selected.

About Vivameda

Vivameda's proprietary historical panel covers 4M+ companies and 48M observed company-year records across 1950–2020 and 100+ countries. The panel was reconstructed retrospectively. Observed professional profiles are not payroll employees; missing is not zero. The synthetic rows contain none of that panel. The separate case study is an approved descriptive summary of retained analysis, not a dataset extract.

Historical reference analysis can support strategy questions. Forecast validation, acquisition inference, commercial performance and current-company transfer require their own evidence and tests. This dataset grants no access to production tools, company data or model weights.

Intended use

Inspect sample responses, discuss integration requirements and prototype how an agent presents evidence limitations. These examples do not specify a stable production MCP API and should not be treated as ground truth for investment decisions.

Contact

For company intelligence, data partnerships or historical context for agent workflows: https://vivameda.com

Version history

v1: 3 synthetic examples, published commit 25cc52273b79f39d094e587083e8b21eb51562f4. v2: 15 synthetic examples, published commit d53842e696ceffd2d34febac7b9d49c8ebba1997. v3: same 15 synthetic rows plus an approved descriptive case study and staged MCP integration documentation.

Downloads last month
44