Datasets:
Languages:
English
Size:
1K<n<10K
Tags:
rag
retrieval-augmented-generation
small-language-models
on-device
domain-adaptation
evaluation
License:
Dataset Preview
The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
The dataset generation failed
Error code: DatasetGenerationError
Exception: TypeError
Message: Couldn't cast array of type
struct<minimum_source_count: int64, primary_skill: string, world_knowledge_shortcut_risk: string, embedded_document_count: int64, authoring_origin: string, difficulty: string>
to
{'answer_value_leakage': Value('bool'), 'authoring_origin': Value('string'), 'confirmatory_evidence': Value('bool'), 'development_only': Value('bool'), 'difficulty': Value('string'), 'explicit_subject_and_relation': Value('bool'), 'minimum_source_count': Value('int64'), 'requested_slots': List(Value('string')), 'topic_bundle': Value('string'), 'world_knowledge_shortcut_risk': Value('string')}
Traceback: Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1827, in _prepare_split_single
for key, table in generator:
^^^^^^^^^
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 613, in wrapped
for item in generator(*args, **kwargs):
~~~~~~~~~^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 343, in _generate_tables
self._cast_table(pa_table, json_field_paths=json_field_paths),
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 132, in _cast_table
pa_table = table_cast(pa_table, self.info.features.arrow_schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2378, in table_cast
return cast_table_to_schema(table, schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2312, in cast_table_to_schema
cast_array_to_feature(
~~~~~~~~~~~~~~~~~~~~~^
table[name] if name in table_column_names else pa.array([None] * len(table), type=schema.field(name).type),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
feature,
^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 1861, in wrapper
return pa.chunked_array([func(chunk, *args, **kwargs) for chunk in array.chunks])
~~~~^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2158, in cast_array_to_feature
raise TypeError(f"Couldn't cast array of type\n{_short_str(array.type)}\nto\n{_short_str(feature)}")
TypeError: Couldn't cast array of type
struct<minimum_source_count: int64, primary_skill: string, world_knowledge_shortcut_risk: string, embedded_document_count: int64, authoring_origin: string, difficulty: string>
to
{'answer_value_leakage': Value('bool'), 'authoring_origin': Value('string'), 'confirmatory_evidence': Value('bool'), 'development_only': Value('bool'), 'difficulty': Value('string'), 'explicit_subject_and_relation': Value('bool'), 'minimum_source_count': Value('int64'), 'requested_slots': List(Value('string')), 'topic_bundle': Value('string'), 'world_knowledge_shortcut_risk': Value('string')}
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/parquet_and_info.py", line 1369, in compute_config_parquet_and_info_response
parquet_operations, partial, estimated_dataset_info = stream_convert_to_parquet(
~~~~~~~~~~~~~~~~~~~~~~~~~^
builder, max_dataset_size_bytes=max_dataset_size_bytes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 948, in stream_convert_to_parquet
builder._prepare_split(split_generator=splits_generators[split], file_format="parquet")
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1694, in _prepare_split
for job_id, done, content in self._prepare_split_single(
~~~~~~~~~~~~~~~~~~~~~~~~~~^
gen_kwargs=gen_kwargs, job_id=job_id, **_prepare_split_args
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
):
^
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1880, in _prepare_split_single
raise DatasetGenerationError("An error occurred while generating the dataset") from e
datasets.exceptions.DatasetGenerationError: An error occurred while generating the datasetNeed help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
answer_units list | canonical_answer string | case_design dict | case_id string | category string | evidence_refs list | expected_terms list | forbidden_terms list | gold_signature string | paths list | propositions list | question string | question_intent string | source_expectations list |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
[
{
"evidence_refs": [
{
"anchor": "Python 3.12 was released on October 2, 2023 as a stable Python release.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_312.md",
"source_id": "python_312",
"start_line":... | Python 3.12 was released on October 2, 2023 as a stable Python release. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"release date",
"release stat... | confirmatory_factual_lookup_001 | factual_lookup | [
{
"anchor": "Python 3.12 was released on October 2, 2023 as a stable Python release.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_312.md",
"source_id": "python_312",
"start_line": 9
}
] | [
"October 2, 2023",
"stable Python release"
] | [] | 7340afd72dca2a074507d832024d6830059e0f38dc9d9280253dd07a6d2079d7 | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_312.md"
] | [
{
"acceptable_paraphrases": [
"Python 3.12 was released on October 2, 2023 as a stable Python release.",
"October 2, 2023 / stable Python release"
],
"canonical_claim": "Python 3.12 was released on October 2, 2023 as a stable Python release.",
"concepts": [
{
"acceptable_su... | According to the Python 3.12 record, what release date and release status does it report? | release date; release status | [
"python_312"
] |
[
{
"evidence_refs": [
{
"anchor": "Python 3.13 was released on October 7, 2024 as a stable Python release.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_313.md",
"source_id": "python_313",
"start_line":... | Python 3.13 was released on October 7, 2024 as a stable Python release. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"release date",
"release stat... | confirmatory_factual_lookup_002 | factual_lookup | [
{
"anchor": "Python 3.13 was released on October 7, 2024 as a stable Python release.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_313.md",
"source_id": "python_313",
"start_line": 9
}
] | [
"October 7, 2024",
"stable Python release"
] | [] | 8b2f67701d402cf28084cfb72f45c8ca7ce304a5bd6e6182e6762461287e756c | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_313.md"
] | [
{
"acceptable_paraphrases": [
"Python 3.13 was released on October 7, 2024 as a stable Python release.",
"October 7, 2024 / stable Python release"
],
"canonical_claim": "Python 3.13 was released on October 7, 2024 as a stable Python release.",
"concepts": [
{
"acceptable_su... | According to the Python 3.13 record, what release date and release status does it report? | release date; release status | [
"python_313"
] |
[
{
"evidence_refs": [
{
"anchor": "PostgreSQL 16 was released on September 14, 2023 with improvements to query parallelism, bulk loading, and logical replication.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresql_16.md... | PostgreSQL 16 was released on September 14, 2023 with improvements to query parallelism, bulk loading, and logical replication. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"release date",
"headline imp... | confirmatory_factual_lookup_003 | factual_lookup | [
{
"anchor": "PostgreSQL 16 was released on September 14, 2023 with improvements to query parallelism, bulk loading, and logical replication.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresql_16.md",
"source_id": "postgresql_16",
"s... | [
"September 14, 2023",
"query parallelism, bulk loading, and logical replication"
] | [] | 195c7692a3c12e03087d9faba04951340fa019c39e740ee5d1866bfed44f5f84 | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresql_16.md"
] | [
{
"acceptable_paraphrases": [
"PostgreSQL 16 was released on September 14, 2023 with improvements to query parallelism, bulk loading, and logical replication.",
"September 14, 2023 / query parallelism, bulk loading, and logical replication"
],
"canonical_claim": "PostgreSQL 16 was released o... | According to the PostgreSQL 16 record, what release date and headline improvement areas does it report? | release date; headline improvement areas | [
"postgresql_16"
] |
[
{
"evidence_refs": [
{
"anchor": "PostgreSQL 17 was released on September 26, 2024 with an overhauled vacuum memory implementation and SQL/JSON JSON_TABLE support.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresql_17.... | PostgreSQL 17 was released on September 26, 2024 with an overhauled vacuum memory implementation and SQL/JSON JSON_TABLE support. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"release date",
"vacuum chang... | confirmatory_factual_lookup_004 | factual_lookup | [
{
"anchor": "PostgreSQL 17 was released on September 26, 2024 with an overhauled vacuum memory implementation and SQL/JSON JSON_TABLE support.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresql_17.md",
"source_id": "postgresql_17",
... | [
"September 26, 2024",
"overhauled vacuum memory implementation",
"JSON_TABLE"
] | [] | 293dba1e378bf2a70adaf3ea502cfef6f7547cb17699b4c555a1cb65f17e4d3f | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresql_17.md"
] | [
{
"acceptable_paraphrases": [
"PostgreSQL 17 was released on September 26, 2024 with an overhauled vacuum memory implementation and SQL/JSON JSON_TABLE support.",
"September 26, 2024 / overhauled vacuum memory implementation / JSON_TABLE"
],
"canonical_claim": "PostgreSQL 17 was released on ... | According to the PostgreSQL 17 record, what release date, vacuum change and SQL/JSON addition does it report? | release date; vacuum change; SQL/JSON addition | [
"postgresql_17"
] |
[
{
"evidence_refs": [
{
"anchor": "Kubernetes 1.30, code-named Uwubernetes, was released on April 17, 2024 with 45 enhancements.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubernetes_130.md",
"source_id": "kubernet... | Kubernetes 1.30, code-named Uwubernetes, was released on April 17, 2024 with 45 enhancements. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"code name",
"release date",
... | confirmatory_factual_lookup_005 | factual_lookup | [
{
"anchor": "Kubernetes 1.30, code-named Uwubernetes, was released on April 17, 2024 with 45 enhancements.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubernetes_130.md",
"source_id": "kubernetes_130",
"start_line": 9
}
] | [
"Uwubernetes",
"April 17, 2024",
"45 enhancements"
] | [] | be2469164e6de4243ff4b09503a4e88729591d72d6903804ccc89295d97dd229 | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubernetes_130.md"
] | [
{
"acceptable_paraphrases": [
"Kubernetes 1.30, code-named Uwubernetes, was released on April 17, 2024 with 45 enhancements.",
"Uwubernetes / April 17, 2024 / 45 enhancements"
],
"canonical_claim": "Kubernetes 1.30, code-named Uwubernetes, was released on April 17, 2024 with 45 enhancements.... | According to the Kubernetes 1.30 record, what code name, release date and enhancement count does it report? | code name; release date; enhancement count | [
"kubernetes_130"
] |
[
{
"evidence_refs": [
{
"anchor": "Kubernetes 1.31, code-named Elli, was released on August 13, 2024 with 45 enhancements.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubernetes_131.md",
"source_id": "kubernetes_131... | Kubernetes 1.31, code-named Elli, was released on August 13, 2024 with 45 enhancements. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"code name",
"release date",
... | confirmatory_factual_lookup_006 | factual_lookup | [
{
"anchor": "Kubernetes 1.31, code-named Elli, was released on August 13, 2024 with 45 enhancements.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubernetes_131.md",
"source_id": "kubernetes_131",
"start_line": 9
}
] | [
"Elli",
"August 13, 2024",
"45 enhancements"
] | [] | 74da0e959dc364194f80597c76def23bdbcf31f8476bf0befecf1cb674d8b1a7 | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubernetes_131.md"
] | [
{
"acceptable_paraphrases": [
"Kubernetes 1.31, code-named Elli, was released on August 13, 2024 with 45 enhancements.",
"Elli / August 13, 2024 / 45 enhancements"
],
"canonical_claim": "Kubernetes 1.31, code-named Elli, was released on August 13, 2024 with 45 enhancements.",
"concepts":... | According to the Kubernetes 1.31 record, what code name, release date and enhancement count does it report? | code name; release date; enhancement count | [
"kubernetes_131"
] |
[
{
"evidence_refs": [
{
"anchor": "NIST released Cybersecurity Framework version 1.1 on April 16, 2018.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/nist_csf_11.md",
"source_id": "nist_csf_11",
"start_line": 9
}
... | NIST released Cybersecurity Framework version 1.1 on April 16, 2018. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"framework version",
"release... | confirmatory_factual_lookup_007 | factual_lookup | [
{
"anchor": "NIST released Cybersecurity Framework version 1.1 on April 16, 2018.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/nist_csf_11.md",
"source_id": "nist_csf_11",
"start_line": 9
}
] | [
"version 1.1",
"April 16, 2018"
] | [] | 4b0543be0ff0ebceea42ade547065ef52925005c73a143848d6d65cc86619f44 | [
"fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/nist_csf_11.md"
] | [
{
"acceptable_paraphrases": [
"NIST released Cybersecurity Framework version 1.1 on April 16, 2018.",
"version 1.1 / April 16, 2018"
],
"canonical_claim": "NIST released Cybersecurity Framework version 1.1 on April 16, 2018.",
"concepts": [
{
"acceptable_surface_forms": [
... | According to the NIST CSF 1.1 record, what framework version and release date does it report? | framework version; release date | [
"nist_csf_11"
] |
[
{
"evidence_refs": [
{
"anchor": "NIST released Cybersecurity Framework version 2.0 on February 26, 2024 as the framework's first major update since 2014.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/nist_csf_20.md",
"source_i... | NIST released Cybersecurity Framework version 2.0 on February 26, 2024 as the framework's first major update since 2014. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"framework version",
"release... | confirmatory_factual_lookup_008 | factual_lookup | [
{
"anchor": "NIST released Cybersecurity Framework version 2.0 on February 26, 2024 as the framework's first major update since 2014.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/nist_csf_20.md",
"source_id": "nist_csf_20",
"start_line": 9
}
] | [
"version 2.0",
"February 26, 2024",
"first major update since 2014"
] | [] | d355755e8391d0a69806c7ef9d33f879991cf7ae7d26304007180674ce654770 | [
"fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/nist_csf_20.md"
] | [
{
"acceptable_paraphrases": [
"NIST released Cybersecurity Framework version 2.0 on February 26, 2024 as the framework's first major update since 2014.",
"version 2.0 / February 26, 2024 / first major update since 2014"
],
"canonical_claim": "NIST released Cybersecurity Framework version 2.0... | According to the NIST CSF 2.0 record, what framework version, release date and historical status does it report? | framework version; release date; historical status | [
"nist_csf_20"
] |
[
{
"evidence_refs": [
{
"anchor": "SLSA 0.1 described a single four-level model covering source, build, provenance, and common requirements.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/slsa_01.md",
"source_id": "slsa_01",
... | SLSA 0.1 described a single four-level model covering source, build, provenance, and common requirements. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"level structure",
"requireme... | confirmatory_factual_lookup_009 | factual_lookup | [
{
"anchor": "SLSA 0.1 described a single four-level model covering source, build, provenance, and common requirements.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/slsa_01.md",
"source_id": "slsa_01",
"start_line": 9
}
] | [
"single four-level model",
"source, build, provenance, and common requirements"
] | [] | 6e01d11ae0359d9fde9a07e89d64b8dd0e07a16d059afad9a38789ec410bf085 | [
"fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/slsa_01.md"
] | [
{
"acceptable_paraphrases": [
"SLSA 0.1 described a single four-level model covering source, build, provenance, and common requirements.",
"single four-level model / source, build, provenance, and common requirements"
],
"canonical_claim": "SLSA 0.1 described a single four-level model coveri... | According to the SLSA 0.1 record, what level structure and requirement areas does it report? | level structure; requirement areas | [
"slsa_01"
] |
[
{
"evidence_refs": [
{
"anchor": "SLSA 1.0 split levels into tracks and defined Build levels 0 through 3.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/slsa_10.md",
"source_id": "slsa_10",
"start_line": 9
}
],... | SLSA 1.0 split levels into tracks and defined Build levels 0 through 3. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"organizational change",
"bui... | confirmatory_factual_lookup_010 | factual_lookup | [
{
"anchor": "SLSA 1.0 split levels into tracks and defined Build levels 0 through 3.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/slsa_10.md",
"source_id": "slsa_10",
"start_line": 9
}
] | [
"split levels into tracks",
"Build levels 0 through 3"
] | [] | bdf567344e65a4adc8efc81163ee4e64bcdd9b77fe1c268cedd728a603c157f7 | [
"fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/slsa_10.md"
] | [
{
"acceptable_paraphrases": [
"SLSA 1.0 split levels into tracks and defined Build levels 0 through 3.",
"split levels into tracks / Build levels 0 through 3"
],
"canonical_claim": "SLSA 1.0 split levels into tracks and defined Build levels 0 through 3.",
"concepts": [
{
"a... | According to the SLSA 1.0 record, what organizational change and build-level range does it report? | organizational change; build-level range | [
"slsa_10"
] |
[
{
"evidence_refs": [
{
"anchor": "RFC 7540 specified HTTP/2 as an Internet Standards Track document published in May 2015.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/technical_standard/http2_7540.md",
"source_id": "http2_7540",
"start_l... | RFC 7540 specified HTTP/2 as an Internet Standards Track document published in May 2015. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"RFC number",
"standards stat... | confirmatory_factual_lookup_011 | factual_lookup | [
{
"anchor": "RFC 7540 specified HTTP/2 as an Internet Standards Track document published in May 2015.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/technical_standard/http2_7540.md",
"source_id": "http2_7540",
"start_line": 9
}
] | [
"RFC 7540",
"Internet Standards Track",
"May 2015"
] | [] | a63b61a7c26a55c417f99ae5412556c2c2c61c4f9d1e98c1a2930e2b29e8adbc | [
"fixtures/answer_ready_confirmatory_transfer_v1/technical_standard/http2_7540.md"
] | [
{
"acceptable_paraphrases": [
"RFC 7540 specified HTTP/2 as an Internet Standards Track document published in May 2015.",
"RFC 7540 / Internet Standards Track / May 2015"
],
"canonical_claim": "RFC 7540 specified HTTP/2 as an Internet Standards Track document published in May 2015.",
"co... | According to the RFC 7540 record, what RFC number, standards status and publication date does it report? | RFC number; standards status; publication date | [
"http2_7540"
] |
[
{
"evidence_refs": [
{
"anchor": "RFC 9113 specified HTTP/2 as an Internet Standards Track document published in June 2022.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/technical_standard/http2_9113.md",
"source_id": "http2_9113",
"start_... | RFC 9113 specified HTTP/2 as an Internet Standards Track document published in June 2022. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"RFC number",
"standards stat... | confirmatory_factual_lookup_012 | factual_lookup | [
{
"anchor": "RFC 9113 specified HTTP/2 as an Internet Standards Track document published in June 2022.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/technical_standard/http2_9113.md",
"source_id": "http2_9113",
"start_line": 9
}
] | [
"RFC 9113",
"Internet Standards Track",
"June 2022"
] | [] | a9426ddc8d1b4c7dbfb25f69f9bcfd1542e39e392100ffc102c2c2b78ba570fe | [
"fixtures/answer_ready_confirmatory_transfer_v1/technical_standard/http2_9113.md"
] | [
{
"acceptable_paraphrases": [
"RFC 9113 specified HTTP/2 as an Internet Standards Track document published in June 2022.",
"RFC 9113 / Internet Standards Track / June 2022"
],
"canonical_claim": "RFC 9113 specified HTTP/2 as an Internet Standards Track document published in June 2022.",
... | According to the RFC 9113 record, what RFC number, standards status and publication date does it report? | RFC number; standards status; publication date | [
"http2_9113"
] |
[
{
"evidence_refs": [
{
"anchor": "NASA's January 9, 2024 update targeted September 2025 for Artemis II and September 2026 for Artemis III.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/artemis_jan_2024.md",
"source_id": "artemis_j... | NASA's January 9, 2024 update targeted September 2025 for Artemis II and September 2026 for Artemis III. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"update date",
"Artemis II ta... | confirmatory_factual_lookup_013 | factual_lookup | [
{
"anchor": "NASA's January 9, 2024 update targeted September 2025 for Artemis II and September 2026 for Artemis III.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/artemis_jan_2024.md",
"source_id": "artemis_jan_2024",
"start_line": 9
}
] | [
"January 9, 2024",
"September 2025 for Artemis II",
"September 2026 for Artemis III"
] | [] | 880f25935a0a5b26fbbce1f489ce8293ff23fe23572c66f961dffa2bfae395ee | [
"fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/artemis_jan_2024.md"
] | [
{
"acceptable_paraphrases": [
"NASA's January 9, 2024 update targeted September 2025 for Artemis II and September 2026 for Artemis III.",
"January 9, 2024 / September 2025 for Artemis II / September 2026 for Artemis III"
],
"canonical_claim": "NASA's January 9, 2024 update targeted September... | According to the January 2024 Artemis schedule record, what update date, Artemis II target and Artemis III target does it report? | update date; Artemis II target; Artemis III target | [
"artemis_jan_2024"
] |
[
{
"evidence_refs": [
{
"anchor": "NASA's December 2024 campaign update moved the Artemis II target to April 2026 and Artemis III to mid-2027.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/artemis_dec_2024.md",
"source_id": "artemi... | NASA's December 2024 campaign update moved the Artemis II target to April 2026 and Artemis III to mid-2027. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"update date",
"Artemis II ta... | confirmatory_factual_lookup_014 | factual_lookup | [
{
"anchor": "NASA's December 2024 campaign update moved the Artemis II target to April 2026 and Artemis III to mid-2027.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/artemis_dec_2024.md",
"source_id": "artemis_dec_2024",
"start_line": 9
}
] | [
"December 2024",
"April 2026",
"mid-2027"
] | [] | 20db491b9cdf780b4e71efce76232b916e5b24dbea47b5f7708bab8aeb7a3232 | [
"fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/artemis_dec_2024.md"
] | [
{
"acceptable_paraphrases": [
"NASA's December 2024 campaign update moved the Artemis II target to April 2026 and Artemis III to mid-2027.",
"December 2024 / April 2026 / mid-2027"
],
"canonical_claim": "NASA's December 2024 campaign update moved the Artemis II target to April 2026 and Artem... | According to the December 2024 Artemis schedule record, what update date, Artemis II target and Artemis III target does it report? | update date; Artemis II target; Artemis III target | [
"artemis_dec_2024"
] |
[
{
"evidence_refs": [
{
"anchor": "Europa Clipper was designed to study whether Jupiter's moon Europa has conditions suitable for life rather than to detect life directly.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/europa_prelaunch.md",... | Europa Clipper was designed to study whether Jupiter's moon Europa has conditions suitable for life rather than to detect life directly. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"science objective",
"detecti... | confirmatory_factual_lookup_015 | factual_lookup | [
{
"anchor": "Europa Clipper was designed to study whether Jupiter's moon Europa has conditions suitable for life rather than to detect life directly.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/europa_prelaunch.md",
"source_id": "europa_prelaunch",
"... | [
"conditions suitable for life",
"rather than to detect life directly"
] | [] | 95b0f1a005e6391d8b7bc5dd0c936f94b56138b5c0b84681ca66ee89ea066ef7 | [
"fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/europa_prelaunch.md"
] | [
{
"acceptable_paraphrases": [
"Europa Clipper was designed to study whether Jupiter's moon Europa has conditions suitable for life rather than to detect life directly.",
"conditions suitable for life / rather than to detect life directly"
],
"canonical_claim": "Europa Clipper was designed to... | According to the Europa Clipper prelaunch plan record, what science objective and detection boundary does it report? | science objective; detection boundary | [
"europa_prelaunch"
] |
[
{
"evidence_refs": [
{
"anchor": "Europa Clipper launched on October 14, 2024 aboard a SpaceX Falcon Heavy from Kennedy Space Center.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/europa_launch.md",
"source_id": "europa_launch",
... | Europa Clipper launched on October 14, 2024 aboard a SpaceX Falcon Heavy from Kennedy Space Center. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"launch date",
"launch vehicl... | confirmatory_factual_lookup_016 | factual_lookup | [
{
"anchor": "Europa Clipper launched on October 14, 2024 aboard a SpaceX Falcon Heavy from Kennedy Space Center.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/europa_launch.md",
"source_id": "europa_launch",
"start_line": 9
}
] | [
"October 14, 2024",
"SpaceX Falcon Heavy",
"Kennedy Space Center"
] | [] | bb86711a557ec2106f06664772c4940b1b73facc7fbe9614b200b94ea642e590 | [
"fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/europa_launch.md"
] | [
{
"acceptable_paraphrases": [
"Europa Clipper launched on October 14, 2024 aboard a SpaceX Falcon Heavy from Kennedy Space Center.",
"October 14, 2024 / SpaceX Falcon Heavy / Kennedy Space Center"
],
"canonical_claim": "Europa Clipper launched on October 14, 2024 aboard a SpaceX Falcon Heavy... | According to the Europa Clipper launch record, what launch date, launch vehicle and launch site does it report? | launch date; launch vehicle; launch site | [
"europa_launch"
] |
[
{
"evidence_refs": [
{
"anchor": "NOAA's GOES-U satellite launched on June 25, 2024 aboard a SpaceX Falcon Heavy.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/goes_u_launch.md",
"source_id": "goes_u_launch",
"start_line":... | NOAA's GOES-U satellite launched on June 25, 2024 aboard a SpaceX Falcon Heavy. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"launch date",
"launch vehicl... | confirmatory_factual_lookup_017 | factual_lookup | [
{
"anchor": "NOAA's GOES-U satellite launched on June 25, 2024 aboard a SpaceX Falcon Heavy.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/goes_u_launch.md",
"source_id": "goes_u_launch",
"start_line": 9
}
] | [
"June 25, 2024",
"SpaceX Falcon Heavy"
] | [] | 938819ebff6668e882de816914b7cb5586d04f051fb97fe4a3863634e76a5934 | [
"fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/goes_u_launch.md"
] | [
{
"acceptable_paraphrases": [
"NOAA's GOES-U satellite launched on June 25, 2024 aboard a SpaceX Falcon Heavy.",
"June 25, 2024 / SpaceX Falcon Heavy"
],
"canonical_claim": "NOAA's GOES-U satellite launched on June 25, 2024 aboard a SpaceX Falcon Heavy.",
"concepts": [
{
"a... | According to the GOES-U launch record, what launch date and launch vehicle does it report? | launch date; launch vehicle | [
"goes_u_launch"
] |
[
{
"evidence_refs": [
{
"anchor": "GOES-19 became NOAA's operational GOES-East satellite on April 7, 2025, replacing GOES-16.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/goes_19_operational.md",
"source_id": "goes_19_operational"... | GOES-19 became NOAA's operational GOES-East satellite on April 7, 2025, replacing GOES-16. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"transition date",
"operation... | confirmatory_factual_lookup_018 | factual_lookup | [
{
"anchor": "GOES-19 became NOAA's operational GOES-East satellite on April 7, 2025, replacing GOES-16.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/goes_19_operational.md",
"source_id": "goes_19_operational",
"start_line": 9
}
] | [
"April 7, 2025",
"operational GOES-East",
"replacing GOES-16"
] | [] | cd3bc379b5bfd662d19e50da58158bcdb1f72e7801a66aed7b0b7dea5450a866 | [
"fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/goes_19_operational.md"
] | [
{
"acceptable_paraphrases": [
"GOES-19 became NOAA's operational GOES-East satellite on April 7, 2025, replacing GOES-16.",
"April 7, 2025 / operational GOES-East / replacing GOES-16"
],
"canonical_claim": "GOES-19 became NOAA's operational GOES-East satellite on April 7, 2025, replacing GOE... | According to the GOES-19 operational transition record, what transition date, operational role and replaced satellite does it report? | transition date; operational role; replaced satellite | [
"goes_19_operational"
] |
[
{
"evidence_refs": [
{
"anchor": "NASA selected Christina Koch as an astronaut in 2013, and she was assigned as an Artemis II mission specialist.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/biography/christina_koch.md",
"source_id": "christina_k... | NASA selected Christina Koch as an astronaut in 2013, and she was assigned as an Artemis II mission specialist. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"selection year",
"Artemis II... | confirmatory_factual_lookup_019 | factual_lookup | [
{
"anchor": "NASA selected Christina Koch as an astronaut in 2013, and she was assigned as an Artemis II mission specialist.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/biography/christina_koch.md",
"source_id": "christina_koch",
"start_line": 9
}
] | [
"selected Christina Koch as an astronaut in 2013",
"Artemis II mission specialist"
] | [] | 6a1c8bd2bbb2a9189540fe1dfb78156be61f770e1835c8eeb436a0000b864fad | [
"fixtures/answer_ready_confirmatory_transfer_v1/biography/christina_koch.md"
] | [
{
"acceptable_paraphrases": [
"NASA selected Christina Koch as an astronaut in 2013, and she was assigned as an Artemis II mission specialist.",
"selected Christina Koch as an astronaut in 2013 / Artemis II mission specialist"
],
"canonical_claim": "NASA selected Christina Koch as an astrona... | According to the Christina Koch record, what selection year and Artemis II role does it report? | selection year; Artemis II role | [
"christina_koch"
] |
[
{
"evidence_refs": [
{
"anchor": "NASA selected Victor Glover as an astronaut in 2013, and he was assigned as the pilot of Artemis II.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/biography/victor_glover.md",
"source_id": "victor_glover",
... | NASA selected Victor Glover as an astronaut in 2013, and he was assigned as the pilot of Artemis II. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"selection year",
"Artemis II... | confirmatory_factual_lookup_020 | factual_lookup | [
{
"anchor": "NASA selected Victor Glover as an astronaut in 2013, and he was assigned as the pilot of Artemis II.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/biography/victor_glover.md",
"source_id": "victor_glover",
"start_line": 9
}
] | [
"selected Victor Glover as an astronaut in 2013",
"pilot of Artemis II"
] | [] | ec57a97210e999e095c36709ac71e2c9603a29555af44900461fad297465c34f | [
"fixtures/answer_ready_confirmatory_transfer_v1/biography/victor_glover.md"
] | [
{
"acceptable_paraphrases": [
"NASA selected Victor Glover as an astronaut in 2013, and he was assigned as the pilot of Artemis II.",
"selected Victor Glover as an astronaut in 2013 / pilot of Artemis II"
],
"canonical_claim": "NASA selected Victor Glover as an astronaut in 2013, and he was ... | According to the Victor Glover record, what selection year and Artemis II role does it report? | selection year; Artemis II role | [
"victor_glover"
] |
[
{
"evidence_refs": [
{
"anchor": "Katherine Johnson joined NACA's West Area Computing unit in 1953 as a research mathematician.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/biography/katherine_johnson.md",
"source_id": "katherine_johnson",
... | Katherine Johnson joined NACA's West Area Computing unit in 1953 as a research mathematician. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"initial unit",
"join year",
... | confirmatory_factual_lookup_021 | factual_lookup | [
{
"anchor": "Katherine Johnson joined NACA's West Area Computing unit in 1953 as a research mathematician.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/biography/katherine_johnson.md",
"source_id": "katherine_johnson",
"start_line": 9
}
] | [
"West Area Computing unit",
"1953",
"research mathematician"
] | [] | 741bbdd4581e586896a81d1b3e1a0c70355c520bfbaa6113fee76c35f25251cf | [
"fixtures/answer_ready_confirmatory_transfer_v1/biography/katherine_johnson.md"
] | [
{
"acceptable_paraphrases": [
"Katherine Johnson joined NACA's West Area Computing unit in 1953 as a research mathematician.",
"West Area Computing unit / 1953 / research mathematician"
],
"canonical_claim": "Katherine Johnson joined NACA's West Area Computing unit in 1953 as a research math... | According to the Katherine Johnson record, what initial unit, join year and job does it report? | initial unit; join year; job | [
"katherine_johnson"
] |
[
{
"evidence_refs": [
{
"anchor": "Dorothy Vaughan joined the NACA in 1943 and became acting head of West Area Computing in 1949.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/biography/dorothy_vaughan.md",
"source_id": "dorothy_vaughan",
"... | Dorothy Vaughan joined the NACA in 1943 and became acting head of West Area Computing in 1949. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"join year",
"management mile... | confirmatory_factual_lookup_022 | factual_lookup | [
{
"anchor": "Dorothy Vaughan joined the NACA in 1943 and became acting head of West Area Computing in 1949.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/biography/dorothy_vaughan.md",
"source_id": "dorothy_vaughan",
"start_line": 9
}
] | [
"joined the NACA in 1943",
"acting head of West Area Computing in 1949"
] | [] | cf08165dd55ffa141fb540dbdb0196737c8c87a4161bfeecf110156170b5530a | [
"fixtures/answer_ready_confirmatory_transfer_v1/biography/dorothy_vaughan.md"
] | [
{
"acceptable_paraphrases": [
"Dorothy Vaughan joined the NACA in 1943 and became acting head of West Area Computing in 1949.",
"joined the NACA in 1943 / acting head of West Area Computing in 1949"
],
"canonical_claim": "Dorothy Vaughan joined the NACA in 1943 and became acting head of West... | According to the Dorothy Vaughan record, what join year and management milestone does it report? | join year; management milestone | [
"dorothy_vaughan"
] |
[
{
"evidence_refs": [
{
"anchor": "The OSIRIS-REx sample capsule landed in Utah on September 24, 2023 after returning material from asteroid Bennu.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/osiris_return.md",
"source_id": "os... | The OSIRIS-REx sample capsule landed in Utah on September 24, 2023 after returning material from asteroid Bennu. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"landing date",
"landing loca... | confirmatory_factual_lookup_023 | factual_lookup | [
{
"anchor": "The OSIRIS-REx sample capsule landed in Utah on September 24, 2023 after returning material from asteroid Bennu.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/osiris_return.md",
"source_id": "osiris_return",
"start_line": 9
}
] | [
"September 24, 2023",
"Utah",
"asteroid Bennu"
] | [] | fa4257b942232a5a55c698cffc795b7d4d73b87954ed253ad508f5b9ec216c73 | [
"fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/osiris_return.md"
] | [
{
"acceptable_paraphrases": [
"The OSIRIS-REx sample capsule landed in Utah on September 24, 2023 after returning material from asteroid Bennu.",
"September 24, 2023 / Utah / asteroid Bennu"
],
"canonical_claim": "The OSIRIS-REx sample capsule landed in Utah on September 24, 2023 after retur... | According to the OSIRIS-REx sample return record, what landing date, landing location and sample source does it report? | landing date; landing location; sample source | [
"osiris_return"
] |
[
{
"evidence_refs": [
{
"anchor": "A 2025 Bennu-sample analysis reported amino acids and all five nucleobases used by life on Earth.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/osiris_analysis.md",
"source_id": "osiris_analysis... | A 2025 Bennu-sample analysis reported amino acids and all five nucleobases used by life on Earth. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"organic-compound finding",
"... | confirmatory_factual_lookup_024 | factual_lookup | [
{
"anchor": "A 2025 Bennu-sample analysis reported amino acids and all five nucleobases used by life on Earth.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/osiris_analysis.md",
"source_id": "osiris_analysis",
"start_line": 9
}
] | [
"amino acids",
"all five nucleobases"
] | [] | 441f5f12859852931ea54ff49f76cbd6ffd91aa32221e0a3920383c6efea2c25 | [
"fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/osiris_analysis.md"
] | [
{
"acceptable_paraphrases": [
"A 2025 Bennu-sample analysis reported amino acids and all five nucleobases used by life on Earth.",
"amino acids / all five nucleobases"
],
"canonical_claim": "A 2025 Bennu-sample analysis reported amino acids and all five nucleobases used by life on Earth.",
... | According to the OSIRIS-REx 2025 analysis record, what organic-compound finding and nucleobase finding does it report? | organic-compound finding; nucleobase finding | [
"osiris_analysis"
] |
[
{
"evidence_refs": [
{
"anchor": "NASA's DART spacecraft intentionally struck the asteroid moonlet Dimorphos on September 26, 2022.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/dart_impact.md",
"source_id": "dart_impact",
... | NASA's DART spacecraft intentionally struck the asteroid moonlet Dimorphos on September 26, 2022. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"target",
"impact date",
... | confirmatory_factual_lookup_025 | factual_lookup | [
{
"anchor": "NASA's DART spacecraft intentionally struck the asteroid moonlet Dimorphos on September 26, 2022.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/dart_impact.md",
"source_id": "dart_impact",
"start_line": 9
}
] | [
"Dimorphos",
"September 26, 2022",
"intentionally struck"
] | [] | 6487559a284efce08eab0fbf5392771a2aa63593713839e4d0fafdd20b998b08 | [
"fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/dart_impact.md"
] | [
{
"acceptable_paraphrases": [
"NASA's DART spacecraft intentionally struck the asteroid moonlet Dimorphos on September 26, 2022.",
"Dimorphos / September 26, 2022 / intentionally struck"
],
"canonical_claim": "NASA's DART spacecraft intentionally struck the asteroid moonlet Dimorphos on Sept... | According to the DART impact outcome record, what target, impact date and impact type does it report? | target; impact date; impact type | [
"dart_impact"
] |
[
{
"evidence_refs": [
{
"anchor": "Follow-up DART analysis found that the impact changed both Dimorphos's orbit and its shape.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/dart_followup.md",
"source_id": "dart_followup",
... | Follow-up DART analysis found that the impact changed both Dimorphos's orbit and its shape. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"orbital effect",
"shape effe... | confirmatory_factual_lookup_026 | factual_lookup | [
{
"anchor": "Follow-up DART analysis found that the impact changed both Dimorphos's orbit and its shape.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/dart_followup.md",
"source_id": "dart_followup",
"start_line": 9
}
] | [
"changed both Dimorphos's orbit",
"its shape"
] | [] | c16ae13b37b0821dabff9a746b640f73e6784ca5cb9086d984bbbedfa25c0929 | [
"fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/dart_followup.md"
] | [
{
"acceptable_paraphrases": [
"Follow-up DART analysis found that the impact changed both Dimorphos's orbit and its shape.",
"changed both Dimorphos's orbit / its shape"
],
"canonical_claim": "Follow-up DART analysis found that the impact changed both Dimorphos's orbit and its shape.",
"... | According to the DART follow-up analysis record, what orbital effect and shape effect does it report? | orbital effect; shape effect | [
"dart_followup"
] |
[
{
"evidence_refs": [
{
"anchor": "NASA released the first full-color James Webb Space Telescope images and spectra on July 12, 2022.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/jwst_first_images.md",
"source_id": "jwst_first_i... | NASA released the first full-color James Webb Space Telescope images and spectra on July 12, 2022. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"release type",
"release date... | confirmatory_factual_lookup_027 | factual_lookup | [
{
"anchor": "NASA released the first full-color James Webb Space Telescope images and spectra on July 12, 2022.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/jwst_first_images.md",
"source_id": "jwst_first_images",
"start_line": 9
}
] | [
"first full-color James Webb Space Telescope images and spectra",
"July 12, 2022"
] | [] | fd76ed531c2c6061f97d45136efa572a1db29b60410204528d1a9d1cdce91b82 | [
"fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/jwst_first_images.md"
] | [
{
"acceptable_paraphrases": [
"NASA released the first full-color James Webb Space Telescope images and spectra on July 12, 2022.",
"first full-color James Webb Space Telescope images and spectra / July 12, 2022"
],
"canonical_claim": "NASA released the first full-color James Webb Space Tele... | According to the Webb first images record, what release type and release date does it report? | release type; release date | [
"jwst_first_images"
] |
[
{
"evidence_refs": [
{
"anchor": "Webb confirmed the rocky exoplanet LHS 475 b in January 2023, making it the telescope's first confirmed exoplanet.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/jwst_lhs475b.md",
"source_id": "j... | Webb confirmed the rocky exoplanet LHS 475 b in January 2023, making it the telescope's first confirmed exoplanet. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"planet",
"announcement date"... | confirmatory_factual_lookup_028 | factual_lookup | [
{
"anchor": "Webb confirmed the rocky exoplanet LHS 475 b in January 2023, making it the telescope's first confirmed exoplanet.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/jwst_lhs475b.md",
"source_id": "jwst_lhs475b",
"start_line": 9
}
] | [
"LHS 475 b",
"January 2023",
"first confirmed exoplanet"
] | [] | 603106f47412cdbc0d9191c6437e56e235853a5e441959867f39da934717f978 | [
"fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/jwst_lhs475b.md"
] | [
{
"acceptable_paraphrases": [
"Webb confirmed the rocky exoplanet LHS 475 b in January 2023, making it the telescope's first confirmed exoplanet.",
"LHS 475 b / January 2023 / first confirmed exoplanet"
],
"canonical_claim": "Webb confirmed the rocky exoplanet LHS 475 b in January 2023, maki... | According to the Webb LHS 475 b result record, what planet, announcement date and Webb status does it report? | planet; announcement date; Webb status | [
"jwst_lhs475b"
] |
[
{
"evidence_refs": [
{
"anchor": "NOAA documented severe coral bleaching in the Florida Keys during record marine heat in summer 2023.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/environmental_science/coral_2023.md",
"source_id": "coral_2023",
... | NOAA documented severe coral bleaching in the Florida Keys during record marine heat in summer 2023. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"location",
"period",
"he... | confirmatory_factual_lookup_029 | factual_lookup | [
{
"anchor": "NOAA documented severe coral bleaching in the Florida Keys during record marine heat in summer 2023.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/environmental_science/coral_2023.md",
"source_id": "coral_2023",
"start_line": 9
}
] | [
"Florida Keys",
"summer 2023",
"record marine heat"
] | [] | 58b7fe8096dfb565bd5040e723ae08234c102e1b9fbdedfc368290887768cd0d | [
"fixtures/answer_ready_confirmatory_transfer_v1/environmental_science/coral_2023.md"
] | [
{
"acceptable_paraphrases": [
"NOAA documented severe coral bleaching in the Florida Keys during record marine heat in summer 2023.",
"Florida Keys / summer 2023 / record marine heat"
],
"canonical_claim": "NOAA documented severe coral bleaching in the Florida Keys during record marine heat ... | According to the 2023 coral bleaching update record, what location, period and heat context does it report? | location; period; heat context | [
"coral_2023"
] |
[
{
"evidence_refs": [
{
"anchor": "NOAA and the International Coral Reef Initiative confirmed the fourth global coral bleaching event on April 15, 2024.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/environmental_science/coral_2024.md",
"source_id"... | NOAA and the International Coral Reef Initiative confirmed the fourth global coral bleaching event on April 15, 2024. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"event number",
"confirmation... | confirmatory_factual_lookup_030 | factual_lookup | [
{
"anchor": "NOAA and the International Coral Reef Initiative confirmed the fourth global coral bleaching event on April 15, 2024.",
"end_line": 9,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/environmental_science/coral_2024.md",
"source_id": "coral_2024",
"start_line": 9
}
] | [
"fourth global coral bleaching event",
"April 15, 2024"
] | [] | b9440f770ec95d38078a4134b271d941438d454838fecb6c6e5ed8b38ab26b10 | [
"fixtures/answer_ready_confirmatory_transfer_v1/environmental_science/coral_2024.md"
] | [
{
"acceptable_paraphrases": [
"NOAA and the International Coral Reef Initiative confirmed the fourth global coral bleaching event on April 15, 2024.",
"fourth global coral bleaching event / April 15, 2024"
],
"canonical_claim": "NOAA and the International Coral Reef Initiative confirmed the ... | According to the 2024 global bleaching declaration record, what event number and confirmation date does it report? | event number; confirmation date | [
"coral_2024"
] |
[
{
"evidence_refs": [
{
"anchor": "Python 3.12 added PEP 695 type-parameter syntax and PEP 701 f-strings integrated into the grammar.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_312.md",
"source_id": "python... | Python 3.12 added PEP 695 type-parameter syntax and PEP 701 f-strings integrated into the grammar. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"generic-typing change",
"f-s... | confirmatory_temporal_current_state_update_001 | temporal_current_state_update | [
{
"anchor": "Python 3.12 added PEP 695 type-parameter syntax and PEP 701 f-strings integrated into the grammar.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_312.md",
"source_id": "python_312",
"start_line": 12
}
] | [
"PEP 695 type-parameter syntax",
"PEP 701 f-strings"
] | [] | bccf461a278c4f61ab7adfe1bb9f6d92e845a1c882c7bc9cdf62c553a7b11aab | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_312.md"
] | [
{
"acceptable_paraphrases": [
"Python 3.12 added PEP 695 type-parameter syntax and PEP 701 f-strings integrated into the grammar.",
"PEP 695 type-parameter syntax / PEP 701 f-strings"
],
"canonical_claim": "Python 3.12 added PEP 695 type-parameter syntax and PEP 701 f-strings integrated into... | For Python 3.12, what does the record report for generic-typing change and f-string grammar change? Include every requested detail. | generic-typing change; f-string grammar change | [
"python_312"
] |
[
{
"evidence_refs": [
{
"anchor": "Python 3.13 added experimental free-threaded execution under PEP 703 and a basic JIT compiler under PEP 744.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_313.md",
"source_id... | Python 3.13 added experimental free-threaded execution under PEP 703 and a basic JIT compiler under PEP 744. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"free-threading status",
"JIT... | confirmatory_temporal_current_state_update_002 | temporal_current_state_update | [
{
"anchor": "Python 3.13 added experimental free-threaded execution under PEP 703 and a basic JIT compiler under PEP 744.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_313.md",
"source_id": "python_313",
"start_line": 12
}
] | [
"experimental free-threaded execution",
"basic JIT compiler"
] | [] | 48117a21edfd7b788406ee4724cd7124d21d755ea5d5c73a8bd577082423c84c | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_313.md"
] | [
{
"acceptable_paraphrases": [
"Python 3.13 added experimental free-threaded execution under PEP 703 and a basic JIT compiler under PEP 744.",
"experimental free-threaded execution / basic JIT compiler"
],
"canonical_claim": "Python 3.13 added experimental free-threaded execution under PEP 70... | For Python 3.13, what does the record report for free-threading status and JIT status? Include every requested detail. | free-threading status; JIT status | [
"python_313"
] |
[
{
"evidence_refs": [
{
"anchor": "PostgreSQL 16 allowed logical replication from a standby instance and let subscribers apply large transactions with parallel workers.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresq... | PostgreSQL 16 allowed logical replication from a standby instance and let subscribers apply large transactions with parallel workers. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"standby replication capability",... | confirmatory_temporal_current_state_update_003 | temporal_current_state_update | [
{
"anchor": "PostgreSQL 16 allowed logical replication from a standby instance and let subscribers apply large transactions with parallel workers.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresql_16.md",
"source_id": "postgresql_16",... | [
"logical replication from a standby instance",
"parallel workers"
] | [] | 7202265dbe22479d56d7c7879d73f16018574473fa39582b03908ffa3438d1c1 | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresql_16.md"
] | [
{
"acceptable_paraphrases": [
"PostgreSQL 16 allowed logical replication from a standby instance and let subscribers apply large transactions with parallel workers.",
"logical replication from a standby instance / parallel workers"
],
"canonical_claim": "PostgreSQL 16 allowed logical replica... | For PostgreSQL 16, what does the record report for standby replication capability and subscriber transaction capability? Include every requested detail. | standby replication capability; subscriber transaction capability | [
"postgresql_16"
] |
[
{
"evidence_refs": [
{
"anchor": "Starting with upgrades from PostgreSQL 17, logical replication slots no longer had to be dropped before a major-version upgrade.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresql_17.... | Starting with upgrades from PostgreSQL 17, logical replication slots no longer had to be dropped before a major-version upgrade. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"version scope",
"replication... | confirmatory_temporal_current_state_update_004 | temporal_current_state_update | [
{
"anchor": "Starting with upgrades from PostgreSQL 17, logical replication slots no longer had to be dropped before a major-version upgrade.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresql_17.md",
"source_id": "postgresql_17",
... | [
"upgrades from PostgreSQL 17",
"slots no longer had to be dropped"
] | [] | 455b4872cf24c4de4617d10463e55a599e9fa3a5b65ea4549844780e7e074f05 | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresql_17.md"
] | [
{
"acceptable_paraphrases": [
"Starting with upgrades from PostgreSQL 17, logical replication slots no longer had to be dropped before a major-version upgrade.",
"upgrades from PostgreSQL 17 / slots no longer had to be dropped"
],
"canonical_claim": "Starting with upgrades from PostgreSQL 17... | For PostgreSQL 17, what does the record report for version scope and replication-slot requirement? Include every requested detail. | version scope; replication-slot requirement | [
"postgresql_17"
] |
[
{
"evidence_refs": [
{
"anchor": "In Kubernetes 1.30, Pod Scheduling Readiness graduated to stable after having reached beta in version 1.27.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubernetes_130.md",
"source... | In Kubernetes 1.30, Pod Scheduling Readiness graduated to stable after having reached beta in version 1.27. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"feature",
"current maturity"... | confirmatory_temporal_current_state_update_005 | temporal_current_state_update | [
{
"anchor": "In Kubernetes 1.30, Pod Scheduling Readiness graduated to stable after having reached beta in version 1.27.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubernetes_130.md",
"source_id": "kubernetes_130",
"start_line": 12
... | [
"Pod Scheduling Readiness",
"graduated to stable",
"beta in version 1.27"
] | [] | 85b59f0d12f68c9f7a959c3651dd57a88b1dd7efbfa0029268bfe9675e7ba98e | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubernetes_130.md"
] | [
{
"acceptable_paraphrases": [
"In Kubernetes 1.30, Pod Scheduling Readiness graduated to stable after having reached beta in version 1.27.",
"Pod Scheduling Readiness / graduated to stable / beta in version 1.27"
],
"canonical_claim": "In Kubernetes 1.30, Pod Scheduling Readiness graduated t... | For Kubernetes 1.30, what does the record report for feature, current maturity and earlier maturity? Include every requested detail. | feature; current maturity; earlier maturity | [
"kubernetes_130"
] |
[
{
"evidence_refs": [
{
"anchor": "AppArmor support became stable in Kubernetes 1.31, while field-based configuration had started in version 1.30.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubernetes_131.md",
"so... | AppArmor support became stable in Kubernetes 1.31, while field-based configuration had started in version 1.30. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"current maturity",
"configur... | confirmatory_temporal_current_state_update_006 | temporal_current_state_update | [
{
"anchor": "AppArmor support became stable in Kubernetes 1.31, while field-based configuration had started in version 1.30.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubernetes_131.md",
"source_id": "kubernetes_131",
"start_line": 1... | [
"AppArmor support became stable",
"field-based configuration",
"version 1.30"
] | [] | 9988dec46fbb92a18838f0469306f47777a5cfe390c9aae3a9ec76415ce39f32 | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubernetes_131.md"
] | [
{
"acceptable_paraphrases": [
"AppArmor support became stable in Kubernetes 1.31, while field-based configuration had started in version 1.30.",
"AppArmor support became stable / field-based configuration / version 1.30"
],
"canonical_claim": "AppArmor support became stable in Kubernetes 1.3... | For Kubernetes 1.31, what does the record report for current maturity, configuration change and change version? Include every requested detail. | current maturity; configuration change; change version | [
"kubernetes_131"
] |
[
{
"evidence_refs": [
{
"anchor": "CSF 1.1 updated guidance on authentication and identity, self-assessment, supply-chain risk, and vulnerability disclosure.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/nist_csf_11.md",
"sourc... | CSF 1.1 updated guidance on authentication and identity, self-assessment, supply-chain risk, and vulnerability disclosure. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"first update area",
"second ... | confirmatory_temporal_current_state_update_007 | temporal_current_state_update | [
{
"anchor": "CSF 1.1 updated guidance on authentication and identity, self-assessment, supply-chain risk, and vulnerability disclosure.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/nist_csf_11.md",
"source_id": "nist_csf_11",
"start_line": 12
}
... | [
"authentication and identity",
"self-assessment",
"supply-chain risk",
"vulnerability disclosure"
] | [] | 393b34ebea5615ef7229f29c10503ca8409e005a5d5e153f2f1b9ea1d8eda041 | [
"fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/nist_csf_11.md"
] | [
{
"acceptable_paraphrases": [
"CSF 1.1 updated guidance on authentication and identity, self-assessment, supply-chain risk, and vulnerability disclosure.",
"authentication and identity / self-assessment / supply-chain risk / vulnerability disclosure"
],
"canonical_claim": "CSF 1.1 updated gu... | For NIST CSF 1.1, what does the record report for first update area, second update area, third update area and fourth update area? Include every requested detail. | first update area; second update area; third update area; fourth update area | [
"nist_csf_11"
] |
[
{
"evidence_refs": [
{
"anchor": "CSF 2.0 expanded its audience from critical infrastructure to organizations of every size and sector and added a sixth core function named Govern.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/nist_cs... | CSF 2.0 expanded its audience from critical infrastructure to organizations of every size and sector and added a sixth core function named Govern. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"expanded audience",
"functio... | confirmatory_temporal_current_state_update_008 | temporal_current_state_update | [
{
"anchor": "CSF 2.0 expanded its audience from critical infrastructure to organizations of every size and sector and added a sixth core function named Govern.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/nist_csf_20.md",
"source_id": "nist_csf_20",
... | [
"organizations of every size and sector",
"sixth core function",
"Govern"
] | [] | 060913ad14d069708ccef1c24a1e2a9bf40b9f6c5355c403ea13d0e0cf191bd4 | [
"fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/nist_csf_20.md"
] | [
{
"acceptable_paraphrases": [
"CSF 2.0 expanded its audience from critical infrastructure to organizations of every size and sector and added a sixth core function named Govern.",
"organizations of every size and sector / sixth core function / Govern"
],
"canonical_claim": "CSF 2.0 expanded ... | For NIST CSF 2.0, what does the record report for expanded audience, function count and new function? Include every requested detail. | expanded audience; function count; new function | [
"nist_csf_20"
] |
[
{
"evidence_refs": [
{
"anchor": "Under SLSA 0.1, a scripted build appeared at level 1, a build service at level 2, and hermetic builds at level 4.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/slsa_01.md",
"source_id": "slsa_... | Under SLSA 0.1, a scripted build appeared at level 1, a build service at level 2, and hermetic builds at level 4. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"level-1 requirement",
"level... | confirmatory_temporal_current_state_update_009 | temporal_current_state_update | [
{
"anchor": "Under SLSA 0.1, a scripted build appeared at level 1, a build service at level 2, and hermetic builds at level 4.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/slsa_01.md",
"source_id": "slsa_01",
"start_line": 12
}
] | [
"a scripted build appeared at level 1",
"a build service at level 2",
"hermetic builds at level 4"
] | [] | 6e22b762cb79b5f02b53395fbf081033f23979a4aba2de1f67fac5569484d193 | [
"fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/slsa_01.md"
] | [
{
"acceptable_paraphrases": [
"Under SLSA 0.1, a scripted build appeared at level 1, a build service at level 2, and hermetic builds at level 4.",
"a scripted build appeared at level 1 / a build service at level 2 / hermetic builds at level 4"
],
"canonical_claim": "Under SLSA 0.1, a scripte... | For SLSA 0.1, what does the record report for level-1 requirement, level-2 requirement and level-4 requirement? Include every requested detail. | level-1 requirement; level-2 requirement; level-4 requirement | [
"slsa_01"
] |
[
{
"evidence_refs": [
{
"anchor": "In SLSA 1.0, Build L1 required provenance, Build L2 required signed provenance from a hosted platform, and Build L3 required a hardened build platform.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/sl... | In SLSA 1.0, Build L1 required provenance, Build L2 required signed provenance from a hosted platform, and Build L3 required a hardened build platform. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"Build L1 requirement",
"Buil... | confirmatory_temporal_current_state_update_010 | temporal_current_state_update | [
{
"anchor": "In SLSA 1.0, Build L1 required provenance, Build L2 required signed provenance from a hosted platform, and Build L3 required a hardened build platform.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/slsa_10.md",
"source_id": "slsa_10",
... | [
"Build L1 required provenance",
"Build L2 required signed provenance",
"Build L3 required a hardened build platform"
] | [] | 639fb38ca90b59512c37522dee46e076032bb3b63027a0724364e7bab3cd6041 | [
"fixtures/answer_ready_confirmatory_transfer_v1/policy_and_standard/slsa_10.md"
] | [
{
"acceptable_paraphrases": [
"In SLSA 1.0, Build L1 required provenance, Build L2 required signed provenance from a hosted platform, and Build L3 required a hardened build platform.",
"Build L1 required provenance / Build L2 required signed provenance / Build L3 required a hardened build platform"
... | For SLSA 1.0, what does the record report for Build L1 requirement, Build L2 requirement and Build L3 requirement? Include every requested detail. | Build L1 requirement; Build L2 requirement; Build L3 requirement | [
"slsa_10"
] |
[
{
"evidence_refs": [
{
"anchor": "RFC 7540 introduced header compression, concurrent exchanges on one connection, and unsolicited server push.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/technical_standard/http2_7540.md",
"source_id": "http2_75... | RFC 7540 introduced header compression, concurrent exchanges on one connection, and unsolicited server push. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"compression capability",
"mu... | confirmatory_temporal_current_state_update_011 | temporal_current_state_update | [
{
"anchor": "RFC 7540 introduced header compression, concurrent exchanges on one connection, and unsolicited server push.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/technical_standard/http2_7540.md",
"source_id": "http2_7540",
"start_line": 12
}
] | [
"header compression",
"concurrent exchanges",
"unsolicited server push"
] | [] | 0ce0b2589ac2524fc5b0a8dd47c14ede7d1e5c92de1bc9194364241930a1692d | [
"fixtures/answer_ready_confirmatory_transfer_v1/technical_standard/http2_7540.md"
] | [
{
"acceptable_paraphrases": [
"RFC 7540 introduced header compression, concurrent exchanges on one connection, and unsolicited server push.",
"header compression / concurrent exchanges / unsolicited server push"
],
"canonical_claim": "RFC 7540 introduced header compression, concurrent exchan... | For RFC 7540, what does the record report for compression capability, multiplexing capability and push capability? Include every requested detail. | compression capability; multiplexing capability; push capability | [
"http2_7540"
] |
[
{
"evidence_refs": [
{
"anchor": "RFC 9113 obsoleted RFC 7540 and RFC 8740 while retaining HTTP/2's field compression and concurrent exchanges.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/technical_standard/http2_9113.md",
"source_id": "http2_9... | RFC 9113 obsoleted RFC 7540 and RFC 8740 while retaining HTTP/2's field compression and concurrent exchanges. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"obsolete RFCs",
"retained co... | confirmatory_temporal_current_state_update_012 | temporal_current_state_update | [
{
"anchor": "RFC 9113 obsoleted RFC 7540 and RFC 8740 while retaining HTTP/2's field compression and concurrent exchanges.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/technical_standard/http2_9113.md",
"source_id": "http2_9113",
"start_line": 12
}
] | [
"obsoleted RFC 7540 and RFC 8740",
"field compression",
"concurrent exchanges"
] | [] | e6117752c1c864b7a3caf76fa226aa7c10f6041296921567f69fdcebb17e18ee | [
"fixtures/answer_ready_confirmatory_transfer_v1/technical_standard/http2_9113.md"
] | [
{
"acceptable_paraphrases": [
"RFC 9113 obsoleted RFC 7540 and RFC 8740 while retaining HTTP/2's field compression and concurrent exchanges.",
"obsoleted RFC 7540 and RFC 8740 / field compression / concurrent exchanges"
],
"canonical_claim": "RFC 9113 obsoleted RFC 7540 and RFC 8740 while re... | For RFC 9113, what does the record report for obsolete RFCs, retained compression and retained multiplexing? Include every requested detail. | obsolete RFCs; retained compression; retained multiplexing | [
"http2_9113"
] |
[
{
"evidence_refs": [
{
"anchor": "The January plan kept Artemis IV, the first mission to the Gateway lunar station, on track for 2028.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/artemis_jan_2024.md",
"source_id": "artemis_jan_... | The January plan kept Artemis IV, the first mission to the Gateway lunar station, on track for 2028. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"mission",
"Gateway role",
... | confirmatory_temporal_current_state_update_013 | temporal_current_state_update | [
{
"anchor": "The January plan kept Artemis IV, the first mission to the Gateway lunar station, on track for 2028.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/artemis_jan_2024.md",
"source_id": "artemis_jan_2024",
"start_line": 12
}
] | [
"Artemis IV",
"first mission to the Gateway lunar station",
"2028"
] | [] | 65ae595e554e9ddece16a195c5d1749bedba620321d8a34446984385439c83e3 | [
"fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/artemis_jan_2024.md"
] | [
{
"acceptable_paraphrases": [
"The January plan kept Artemis IV, the first mission to the Gateway lunar station, on track for 2028.",
"Artemis IV / first mission to the Gateway lunar station / 2028"
],
"canonical_claim": "The January plan kept Artemis IV, the first mission to the Gateway lun... | For January 2024 Artemis schedule, what does the record report for mission, Gateway role and target year? Include every requested detail. | mission; Gateway role; target year | [
"artemis_jan_2024"
] |
[
{
"evidence_refs": [
{
"anchor": "NASA retained the Artemis II Orion heat shield and changed the return trajectory to control how it encountered Earth's atmosphere.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/artemis_dec_2024.md",
... | NASA retained the Artemis II Orion heat shield and changed the return trajectory to control how it encountered Earth's atmosphere. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"heat-shield decision",
"traj... | confirmatory_temporal_current_state_update_014 | temporal_current_state_update | [
{
"anchor": "NASA retained the Artemis II Orion heat shield and changed the return trajectory to control how it encountered Earth's atmosphere.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/artemis_dec_2024.md",
"source_id": "artemis_dec_2024",
"start... | [
"retained the Artemis II Orion heat shield",
"changed the return trajectory"
] | [] | 45b27916d2ce843be9d8c125831ba83e5c7ee74bfcbd033282a3f0b4d4c81530 | [
"fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/artemis_dec_2024.md"
] | [
{
"acceptable_paraphrases": [
"NASA retained the Artemis II Orion heat shield and changed the return trajectory to control how it encountered Earth's atmosphere.",
"retained the Artemis II Orion heat shield / changed the return trajectory"
],
"canonical_claim": "NASA retained the Artemis II ... | For December 2024 Artemis schedule, what does the record report for heat-shield decision and trajectory response? Include every requested detail. | heat-shield decision; trajectory response | [
"artemis_dec_2024"
] |
[
{
"evidence_refs": [
{
"anchor": "The mission plan called for nearly 50 Europa flybys after arrival at Jupiter in April 2030.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/europa_prelaunch.md",
"source_id": "europa_prelaunch",
... | The mission plan called for nearly 50 Europa flybys after arrival at Jupiter in April 2030. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"flyby count",
"planned arriv... | confirmatory_temporal_current_state_update_015 | temporal_current_state_update | [
{
"anchor": "The mission plan called for nearly 50 Europa flybys after arrival at Jupiter in April 2030.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/europa_prelaunch.md",
"source_id": "europa_prelaunch",
"start_line": 12
}
] | [
"nearly 50 Europa flybys",
"April 2030"
] | [] | c5bfe8549cc83ac68fe66d36fe68dcb8cade83c1adfea478b7c731b5401337c6 | [
"fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/europa_prelaunch.md"
] | [
{
"acceptable_paraphrases": [
"The mission plan called for nearly 50 Europa flybys after arrival at Jupiter in April 2030.",
"nearly 50 Europa flybys / April 2030"
],
"canonical_claim": "The mission plan called for nearly 50 Europa flybys after arrival at Jupiter in April 2030.",
"concep... | For Europa Clipper prelaunch plan, what does the record report for flyby count and planned arrival? Include every requested detail. | flyby count; planned arrival | [
"europa_prelaunch"
] |
[
{
"evidence_refs": [
{
"anchor": "The launched spacecraft began a journey of about 1.8 billion miles toward an expected Jupiter arrival in April 2030.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/europa_launch.md",
"source_id": ... | The launched spacecraft began a journey of about 1.8 billion miles toward an expected Jupiter arrival in April 2030. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"journey distance",
"expected... | confirmatory_temporal_current_state_update_016 | temporal_current_state_update | [
{
"anchor": "The launched spacecraft began a journey of about 1.8 billion miles toward an expected Jupiter arrival in April 2030.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/europa_launch.md",
"source_id": "europa_launch",
"start_line": 12
}
] | [
"about 1.8 billion miles",
"April 2030"
] | [] | a639f7876f6700e411c244b197e9968da7488297e867cbe2c30a170f84b1e698 | [
"fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/europa_launch.md"
] | [
{
"acceptable_paraphrases": [
"The launched spacecraft began a journey of about 1.8 billion miles toward an expected Jupiter arrival in April 2030.",
"about 1.8 billion miles / April 2030"
],
"canonical_claim": "The launched spacecraft began a journey of about 1.8 billion miles toward an exp... | For Europa Clipper launch, what does the record report for journey distance and expected arrival? Include every requested detail. | journey distance; expected arrival | [
"europa_launch"
] |
[
{
"evidence_refs": [
{
"anchor": "After reaching geostationary orbit, GOES-U was scheduled to be renamed GOES-19 and undergo post-launch testing.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/goes_u_launch.md",
"source_id": "goes... | After reaching geostationary orbit, GOES-U was scheduled to be renamed GOES-19 and undergo post-launch testing. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"operational name",
"next pha... | confirmatory_temporal_current_state_update_017 | temporal_current_state_update | [
{
"anchor": "After reaching geostationary orbit, GOES-U was scheduled to be renamed GOES-19 and undergo post-launch testing.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/goes_u_launch.md",
"source_id": "goes_u_launch",
"start_line": 12
}
] | [
"renamed GOES-19",
"post-launch testing"
] | [] | 2292510a5c01ed81acfebf899e2dfc01051715dbb2dc0d3c8ff55e65f258a6c4 | [
"fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/goes_u_launch.md"
] | [
{
"acceptable_paraphrases": [
"After reaching geostationary orbit, GOES-U was scheduled to be renamed GOES-19 and undergo post-launch testing.",
"renamed GOES-19 / post-launch testing"
],
"canonical_claim": "After reaching geostationary orbit, GOES-U was scheduled to be renamed GOES-19 and u... | For GOES-U launch, what does the record report for operational name and next phase? Include every requested detail. | operational name; next phase | [
"goes_u_launch"
] |
[
{
"evidence_refs": [
{
"anchor": "GOES-19 carried the first operational space-based coronagraph dedicated to continuous monitoring of the Sun's corona.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/goes_19_operational.md",
"sourc... | GOES-19 carried the first operational space-based coronagraph dedicated to continuous monitoring of the Sun's corona. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"instrument status",
"monitor... | confirmatory_temporal_current_state_update_018 | temporal_current_state_update | [
{
"anchor": "GOES-19 carried the first operational space-based coronagraph dedicated to continuous monitoring of the Sun's corona.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/goes_19_operational.md",
"source_id": "goes_19_operational",
"start_line":... | [
"first operational space-based coronagraph",
"continuous monitoring of the Sun's corona"
] | [] | e1ed7a9f1b55d1ad6b4719a4e79d6a24dad23f0ec5f2708f79ad3ecc3a57dd19 | [
"fixtures/answer_ready_confirmatory_transfer_v1/project_timeline/goes_19_operational.md"
] | [
{
"acceptable_paraphrases": [
"GOES-19 carried the first operational space-based coronagraph dedicated to continuous monitoring of the Sun's corona.",
"first operational space-based coronagraph / continuous monitoring of the Sun's corona"
],
"canonical_claim": "GOES-19 carried the first oper... | For GOES-19 operational transition, what does the record report for instrument status and monitoring purpose? Include every requested detail. | instrument status; monitoring purpose | [
"goes_19_operational"
] |
[
{
"evidence_refs": [
{
"anchor": "Koch launched to the International Space Station in March 2019 and returned in February 2020 after 328 days.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/biography/christina_koch.md",
"source_id": "christina_koc... | Koch launched to the International Space Station in March 2019 and returned in February 2020 after 328 days. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"launch month",
"return month... | confirmatory_temporal_current_state_update_019 | temporal_current_state_update | [
{
"anchor": "Koch launched to the International Space Station in March 2019 and returned in February 2020 after 328 days.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/biography/christina_koch.md",
"source_id": "christina_koch",
"start_line": 12
}
] | [
"March 2019",
"February 2020",
"328 days"
] | [] | 37203edf600da133ce954e155b82fbca179e12891754d0506504264bed956dc9 | [
"fixtures/answer_ready_confirmatory_transfer_v1/biography/christina_koch.md"
] | [
{
"acceptable_paraphrases": [
"Koch launched to the International Space Station in March 2019 and returned in February 2020 after 328 days.",
"March 2019 / February 2020 / 328 days"
],
"canonical_claim": "Koch launched to the International Space Station in March 2019 and returned in February... | For Christina Koch, what does the record report for launch month, return month and mission duration? Include every requested detail. | launch month; return month; mission duration | [
"christina_koch"
] |
[
{
"evidence_refs": [
{
"anchor": "Glover launched as pilot of SpaceX Crew-1 in November 2020 and returned in May 2021 after 168 days in space.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/biography/victor_glover.md",
"source_id": "victor_glover"... | Glover launched as pilot of SpaceX Crew-1 in November 2020 and returned in May 2021 after 168 days in space. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"launch month",
"return month... | confirmatory_temporal_current_state_update_020 | temporal_current_state_update | [
{
"anchor": "Glover launched as pilot of SpaceX Crew-1 in November 2020 and returned in May 2021 after 168 days in space.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/biography/victor_glover.md",
"source_id": "victor_glover",
"start_line": 12
}
] | [
"November 2020",
"May 2021",
"168 days"
] | [] | a73234dcbe19428686e3b7f82ee21d748e923eac3ebc0846e3848d5b49226b6b | [
"fixtures/answer_ready_confirmatory_transfer_v1/biography/victor_glover.md"
] | [
{
"acceptable_paraphrases": [
"Glover launched as pilot of SpaceX Crew-1 in November 2020 and returned in May 2021 after 168 days in space.",
"November 2020 / May 2021 / 168 days"
],
"canonical_claim": "Glover launched as pilot of SpaceX Crew-1 in November 2020 and returned in May 2021 after... | For Victor Glover, what does the record report for launch month, return month and mission duration? Include every requested detail. | launch month; return month; mission duration | [
"victor_glover"
] |
[
{
"evidence_refs": [
{
"anchor": "Johnson calculated the trajectory for Alan Shepard's 1961 mission and later verified John Glenn's 1962 orbital calculations.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/biography/katherine_johnson.md",
"source_... | Johnson calculated the trajectory for Alan Shepard's 1961 mission and later verified John Glenn's 1962 orbital calculations. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"earlier calculation",
"later... | confirmatory_temporal_current_state_update_021 | temporal_current_state_update | [
{
"anchor": "Johnson calculated the trajectory for Alan Shepard's 1961 mission and later verified John Glenn's 1962 orbital calculations.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/biography/katherine_johnson.md",
"source_id": "katherine_johnson",
"start_line": 12
... | [
"Alan Shepard's 1961 mission",
"verified John Glenn's 1962 orbital calculations"
] | [] | aebf6a430d130586db024e3cf3300b6b5b4e93f2598703ccfaa90d10f9c4bdb7 | [
"fixtures/answer_ready_confirmatory_transfer_v1/biography/katherine_johnson.md"
] | [
{
"acceptable_paraphrases": [
"Johnson calculated the trajectory for Alan Shepard's 1961 mission and later verified John Glenn's 1962 orbital calculations.",
"Alan Shepard's 1961 mission / verified John Glenn's 1962 orbital calculations"
],
"canonical_claim": "Johnson calculated the trajecto... | For Katherine Johnson, what does the record report for earlier calculation and later verification? Include every requested detail. | earlier calculation; later verification | [
"katherine_johnson"
] |
[
{
"evidence_refs": [
{
"anchor": "As machine computing expanded, Vaughan learned FORTRAN and taught the language to colleagues for work on IBM systems.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/biography/dorothy_vaughan.md",
"source_id": "dor... | As machine computing expanded, Vaughan learned FORTRAN and taught the language to colleagues for work on IBM systems. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"new language",
"training rol... | confirmatory_temporal_current_state_update_022 | temporal_current_state_update | [
{
"anchor": "As machine computing expanded, Vaughan learned FORTRAN and taught the language to colleagues for work on IBM systems.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/biography/dorothy_vaughan.md",
"source_id": "dorothy_vaughan",
"start_line": 12
}
] | [
"learned FORTRAN",
"taught the language to colleagues",
"IBM systems"
] | [] | 1f6d5597307b3ace4fcceee9fe970e2618e8c0f31187811a0aadb0dbaf38f14d | [
"fixtures/answer_ready_confirmatory_transfer_v1/biography/dorothy_vaughan.md"
] | [
{
"acceptable_paraphrases": [
"As machine computing expanded, Vaughan learned FORTRAN and taught the language to colleagues for work on IBM systems.",
"learned FORTRAN / taught the language to colleagues / IBM systems"
],
"canonical_claim": "As machine computing expanded, Vaughan learned FOR... | For Dorothy Vaughan, what does the record report for new language, training role and target systems? Include every requested detail. | new language; training role; target systems | [
"dorothy_vaughan"
] |
[
{
"evidence_refs": [
{
"anchor": "NASA's initial examination reported carbon and water-bearing clay minerals in the Bennu material.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/osiris_return.md",
"source_id": "osiris_return",
... | NASA's initial examination reported carbon and water-bearing clay minerals in the Bennu material. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"first finding",
"second find... | confirmatory_temporal_current_state_update_023 | temporal_current_state_update | [
{
"anchor": "NASA's initial examination reported carbon and water-bearing clay minerals in the Bennu material.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/osiris_return.md",
"source_id": "osiris_return",
"start_line": 12
}
] | [
"carbon",
"water-bearing clay minerals"
] | [] | 4bd552b8a60f1177b1d6c1f25f9532fc35dffa1387062967118150e2bab0a93d | [
"fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/osiris_return.md"
] | [
{
"acceptable_paraphrases": [
"NASA's initial examination reported carbon and water-bearing clay minerals in the Bennu material.",
"carbon / water-bearing clay minerals"
],
"canonical_claim": "NASA's initial examination reported carbon and water-bearing clay minerals in the Bennu material.",... | For OSIRIS-REx sample return, what does the record report for first finding and second finding? Include every requested detail. | first finding; second finding | [
"osiris_return"
] |
[
{
"evidence_refs": [
{
"anchor": "The analysis also identified salts formed as water evaporated from an ancient brine on Bennu's parent body.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/osiris_analysis.md",
"source_id": "osir... | The analysis also identified salts formed as water evaporated from an ancient brine on Bennu's parent body. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"material",
"formation proces... | confirmatory_temporal_current_state_update_024 | temporal_current_state_update | [
{
"anchor": "The analysis also identified salts formed as water evaporated from an ancient brine on Bennu's parent body.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/osiris_analysis.md",
"source_id": "osiris_analysis",
"start_line": 12
}
] | [
"salts",
"water evaporated",
"ancient brine"
] | [] | 2d2fcd3d39db99d73f3a547363638cbbd96ccc2dc10d725676827a5694cb1154 | [
"fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/osiris_analysis.md"
] | [
{
"acceptable_paraphrases": [
"The analysis also identified salts formed as water evaporated from an ancient brine on Bennu's parent body.",
"salts / water evaporated / ancient brine"
],
"canonical_claim": "The analysis also identified salts formed as water evaporated from an ancient brine o... | For OSIRIS-REx 2025 analysis, what does the record report for material, formation process and source environment? Include every requested detail. | material; formation process; source environment | [
"osiris_analysis"
] |
[
{
"evidence_refs": [
{
"anchor": "The impact shortened Dimorphos's orbit around Didymos by 32 minutes, from 11 hours 55 minutes to 11 hours 23 minutes.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/dart_impact.md",
"source_id":... | The impact shortened Dimorphos's orbit around Didymos by 32 minutes, from 11 hours 55 minutes to 11 hours 23 minutes. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"period change",
"before peri... | confirmatory_temporal_current_state_update_025 | temporal_current_state_update | [
{
"anchor": "The impact shortened Dimorphos's orbit around Didymos by 32 minutes, from 11 hours 55 minutes to 11 hours 23 minutes.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/dart_impact.md",
"source_id": "dart_impact",
"start_line": 12
}
] | [
"shortened Dimorphos's orbit around Didymos by 32 minutes",
"11 hours 55 minutes",
"11 hours 23 minutes"
] | [] | ddebd484b7703b085bbe558921dc8cc5d7f87f994d430c2504534fff6b097d44 | [
"fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/dart_impact.md"
] | [
{
"acceptable_paraphrases": [
"The impact shortened Dimorphos's orbit around Didymos by 32 minutes, from 11 hours 55 minutes to 11 hours 23 minutes.",
"shortened Dimorphos's orbit around Didymos by 32 minutes / 11 hours 55 minutes / 11 hours 23 minutes"
],
"canonical_claim": "The impact shor... | For DART impact outcome, what does the record report for period change, before period and after period? Include every requested detail. | period change; before period; after period | [
"dart_impact"
] |
[
{
"evidence_refs": [
{
"anchor": "Dimorphos changed from a roughly symmetrical oblate spheroid to a more elongated triaxial ellipsoid after impact.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/dart_followup.md",
"source_id": "... | Dimorphos changed from a roughly symmetrical oblate spheroid to a more elongated triaxial ellipsoid after impact. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"before shape",
"after shape"... | confirmatory_temporal_current_state_update_026 | temporal_current_state_update | [
{
"anchor": "Dimorphos changed from a roughly symmetrical oblate spheroid to a more elongated triaxial ellipsoid after impact.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/dart_followup.md",
"source_id": "dart_followup",
"start_line": 12
}
] | [
"oblate spheroid",
"elongated triaxial ellipsoid"
] | [] | 2f7d25ec9a5f6d2a9a4ea91b08976b51c58b6591216f033b00d254dfc3a3f2ee | [
"fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/dart_followup.md"
] | [
{
"acceptable_paraphrases": [
"Dimorphos changed from a roughly symmetrical oblate spheroid to a more elongated triaxial ellipsoid after impact.",
"oblate spheroid / elongated triaxial ellipsoid"
],
"canonical_claim": "Dimorphos changed from a roughly symmetrical oblate spheroid to a more el... | For DART follow-up analysis, what does the record report for before shape and after shape? Include every requested detail. | before shape; after shape | [
"dart_followup"
] |
[
{
"evidence_refs": [
{
"anchor": "Webb's First Deep Field imaged the galaxy cluster SMACS 0723 and used about 12.5 hours of observing time.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/jwst_first_images.md",
"source_id": "jwst... | Webb's First Deep Field imaged the galaxy cluster SMACS 0723 and used about 12.5 hours of observing time. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"target",
"observing time"
... | confirmatory_temporal_current_state_update_027 | temporal_current_state_update | [
{
"anchor": "Webb's First Deep Field imaged the galaxy cluster SMACS 0723 and used about 12.5 hours of observing time.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/jwst_first_images.md",
"source_id": "jwst_first_images",
"start_line": 12
}
] | [
"SMACS 0723",
"about 12.5 hours"
] | [] | fd746b6c1c23d7baff7cfc15bdbadd025cdee91627a5606f1f9247049e57c7b2 | [
"fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/jwst_first_images.md"
] | [
{
"acceptable_paraphrases": [
"Webb's First Deep Field imaged the galaxy cluster SMACS 0723 and used about 12.5 hours of observing time.",
"SMACS 0723 / about 12.5 hours"
],
"canonical_claim": "Webb's First Deep Field imaged the galaxy cluster SMACS 0723 and used about 12.5 hours of observin... | For Webb first images, what does the record report for target and observing time? Include every requested detail. | target; observing time | [
"jwst_first_images"
] |
[
{
"evidence_refs": [
{
"anchor": "Two Webb transits showed that LHS 475 b was about 99 percent of Earth's diameter.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/jwst_lhs475b.md",
"source_id": "jwst_lhs475b",
"start_lin... | Two Webb transits showed that LHS 475 b was about 99 percent of Earth's diameter. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"observation count",
"size me... | confirmatory_temporal_current_state_update_028 | temporal_current_state_update | [
{
"anchor": "Two Webb transits showed that LHS 475 b was about 99 percent of Earth's diameter.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/jwst_lhs475b.md",
"source_id": "jwst_lhs475b",
"start_line": 12
}
] | [
"two Webb transits",
"99 percent of Earth's diameter"
] | [] | 5bad7c996461631813b6d7be3f33dc41a41233e44d2782847cb84dbf89060597 | [
"fixtures/answer_ready_confirmatory_transfer_v1/scientific_project/jwst_lhs475b.md"
] | [
{
"acceptable_paraphrases": [
"Two Webb transits showed that LHS 475 b was about 99 percent of Earth's diameter.",
"two Webb transits / 99 percent of Earth's diameter"
],
"canonical_claim": "Two Webb transits showed that LHS 475 b was about 99 percent of Earth's diameter.",
"concepts": [... | For Webb LHS 475 b result, what does the record report for observation count and size measurement? Include every requested detail. | observation count; size measurement | [
"jwst_lhs475b"
] |
[
{
"evidence_refs": [
{
"anchor": "Managers moved nursery corals to cooler land-based facilities and deeper water as heat stress intensified.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/environmental_science/coral_2023.md",
"source_id": "coral_2... | Managers moved nursery corals to cooler land-based facilities and deeper water as heat stress intensified. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"management action",
"first r... | confirmatory_temporal_current_state_update_029 | temporal_current_state_update | [
{
"anchor": "Managers moved nursery corals to cooler land-based facilities and deeper water as heat stress intensified.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/environmental_science/coral_2023.md",
"source_id": "coral_2023",
"start_line": 12
}
] | [
"moved nursery corals",
"cooler land-based facilities",
"deeper water"
] | [] | cb22cfd3584fb87acfe521c6ab8c1f4246b62cebcc884c916ba796f382407c7e | [
"fixtures/answer_ready_confirmatory_transfer_v1/environmental_science/coral_2023.md"
] | [
{
"acceptable_paraphrases": [
"Managers moved nursery corals to cooler land-based facilities and deeper water as heat stress intensified.",
"moved nursery corals / cooler land-based facilities / deeper water"
],
"canonical_claim": "Managers moved nursery corals to cooler land-based facilitie... | For 2023 coral bleaching update, what does the record report for management action, first refuge and second refuge? Include every requested detail. | management action; first refuge; second refuge | [
"coral_2023"
] |
[
{
"evidence_refs": [
{
"anchor": "From February 2023 through April 2024, mass bleaching was documented in both the Northern and Southern Hemispheres.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/environmental_science/coral_2024.md",
"source_id":... | From February 2023 through April 2024, mass bleaching was documented in both the Northern and Southern Hemispheres. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "medium",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"observation period",
"hemisp... | confirmatory_temporal_current_state_update_030 | temporal_current_state_update | [
{
"anchor": "From February 2023 through April 2024, mass bleaching was documented in both the Northern and Southern Hemispheres.",
"end_line": 12,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/environmental_science/coral_2024.md",
"source_id": "coral_2024",
"start_line": 12
}
] | [
"February 2023 through April 2024",
"Northern and Southern Hemispheres"
] | [] | 4cfc7fae0435fd150a954ff5b8b9fc7d414c45722300866d8ab74a4465a794b9 | [
"fixtures/answer_ready_confirmatory_transfer_v1/environmental_science/coral_2024.md"
] | [
{
"acceptable_paraphrases": [
"From February 2023 through April 2024, mass bleaching was documented in both the Northern and Southern Hemispheres.",
"February 2023 through April 2024 / Northern and Southern Hemispheres"
],
"canonical_claim": "From February 2023 through April 2024, mass bleac... | For 2024 global bleaching declaration, what does the record report for observation period and hemisphere coverage? Include every requested detail. | observation period; hemisphere coverage | [
"coral_2024"
] |
[
{
"evidence_refs": [
{
"anchor": "Python 3.12 removed distutils from the standard library, while third-party Setuptools continued to provide distutils.",
"end_line": 15,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_312.md",
"... | Python 3.12 removed distutils from the standard library, while third-party Setuptools continued to provide distutils. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "hard",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"standard-library status",
"thi... | confirmatory_contradiction_stale_info_001 | contradiction_stale_info | [
{
"anchor": "Python 3.12 removed distutils from the standard library, while third-party Setuptools continued to provide distutils.",
"end_line": 15,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_312.md",
"source_id": "python_312",
"start_line": 15
... | [
"removed distutils from the standard library",
"Setuptools continued to provide distutils"
] | [
"distutils remained in the Python 3.12 standard library"
] | 8e2e8eeaf67cefe9b7838adba7fac6439171400de8fa22cd5dd77565d5c89a2a | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_312.md"
] | [
{
"acceptable_paraphrases": [
"Python 3.12 removed distutils from the standard library, while third-party Setuptools continued to provide distutils.",
"removed distutils from the standard library / Setuptools continued to provide distutils"
],
"canonical_claim": "Python 3.12 removed distutil... | The claim "distutils remained in the Python 3.12 standard library" is being checked against the Python 3.12 record. What does the source support instead regarding standard-library status and third-party availability? | standard-library status; third-party availability | [
"python_312"
] |
[
{
"evidence_refs": [
{
"anchor": "The Python 3.13 JIT was disabled by default and its initial performance improvements were described as modest.",
"end_line": 15,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_313.md",
"source_... | The Python 3.13 JIT was disabled by default and its initial performance improvements were described as modest. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "hard",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"default JIT state",
"performan... | confirmatory_contradiction_stale_info_002 | contradiction_stale_info | [
{
"anchor": "The Python 3.13 JIT was disabled by default and its initial performance improvements were described as modest.",
"end_line": 15,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_313.md",
"source_id": "python_313",
"start_line": 15
}
] | [
"disabled by default",
"initial performance improvements were described as modest"
] | [
"the Python 3.13 JIT was enabled by default and delivered large guaranteed speedups"
] | 2ea0edd9b7de1ff3634e7c836875c45bfd9e98b584f911b5c893ec38c4bf8467 | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/python_313.md"
] | [
{
"acceptable_paraphrases": [
"The Python 3.13 JIT was disabled by default and its initial performance improvements were described as modest.",
"disabled by default / initial performance improvements were described as modest"
],
"canonical_claim": "The Python 3.13 JIT was disabled by default... | The claim "the Python 3.13 JIT was enabled by default and delivered large guaranteed speedups" is being checked against the Python 3.13 record. What does the source support instead regarding default JIT state and performance boundary? | default JIT state; performance boundary | [
"python_313"
] |
[
{
"evidence_refs": [
{
"anchor": "PostgreSQL 16 COPY tests showed up to a 300 percent improvement in some cases, not a universal 300 percent gain for every workload.",
"end_line": 15,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresql_... | PostgreSQL 16 COPY tests showed up to a 300 percent improvement in some cases, not a universal 300 percent gain for every workload. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "hard",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"reported maximum",
"scope qual... | confirmatory_contradiction_stale_info_003 | contradiction_stale_info | [
{
"anchor": "PostgreSQL 16 COPY tests showed up to a 300 percent improvement in some cases, not a universal 300 percent gain for every workload.",
"end_line": 15,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresql_16.md",
"source_id": "postgresql_16",
... | [
"up to a 300 percent improvement",
"in some cases"
] | [
"every PostgreSQL 16 workload became 300 percent faster"
] | 967b9286706e37b71998e346fc92331e916c35f777a07f82602ab974cc65fc19 | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresql_16.md"
] | [
{
"acceptable_paraphrases": [
"PostgreSQL 16 COPY tests showed up to a 300 percent improvement in some cases, not a universal 300 percent gain for every workload.",
"up to a 300 percent improvement / in some cases"
],
"canonical_claim": "PostgreSQL 16 COPY tests showed up to a 300 percent im... | The claim "every PostgreSQL 16 workload became 300 percent faster" is being checked against the PostgreSQL 16 record. What does the source support instead regarding reported maximum and scope qualifier? | reported maximum; scope qualifier | [
"postgresql_16"
] |
[
{
"evidence_refs": [
{
"anchor": "The new PostgreSQL 17 vacuum structure could use up to 20 times less memory; that figure described vacuum memory, not total database memory.",
"end_line": 15,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/po... | The new PostgreSQL 17 vacuum structure could use up to 20 times less memory; that figure described vacuum memory, not total database memory. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "hard",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"reported maximum",
"measured s... | confirmatory_contradiction_stale_info_004 | contradiction_stale_info | [
{
"anchor": "The new PostgreSQL 17 vacuum structure could use up to 20 times less memory; that figure described vacuum memory, not total database memory.",
"end_line": 15,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresql_17.md",
"source_id": "postgres... | [
"up to 20 times less memory",
"vacuum memory"
] | [
"PostgreSQL 17 always used 20 times less total database memory"
] | 390fa65f83b9e164f5d8e94b9245b16bacd0667e2921b7404333e4bb064fbaad | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/postgresql_17.md"
] | [
{
"acceptable_paraphrases": [
"The new PostgreSQL 17 vacuum structure could use up to 20 times less memory; that figure described vacuum memory, not total database memory.",
"up to 20 times less memory / vacuum memory"
],
"canonical_claim": "The new PostgreSQL 17 vacuum structure could use u... | The claim "PostgreSQL 17 always used 20 times less total database memory" is being checked against the PostgreSQL 17 record. What does the source support instead regarding reported maximum and measured subsystem? | reported maximum; measured subsystem | [
"postgresql_17"
] |
[
{
"evidence_refs": [
{
"anchor": "Node log query was beta in Kubernetes 1.30 but still required the feature gate and both kubelet log-query settings to be enabled.",
"end_line": 15,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubernetes_13... | Node log query was beta in Kubernetes 1.30 but still required the feature gate and both kubelet log-query settings to be enabled. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "hard",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"maturity",
"activation require... | confirmatory_contradiction_stale_info_005 | contradiction_stale_info | [
{
"anchor": "Node log query was beta in Kubernetes 1.30 but still required the feature gate and both kubelet log-query settings to be enabled.",
"end_line": 15,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubernetes_130.md",
"source_id": "kubernetes_130",
... | [
"beta in Kubernetes 1.30",
"feature gate",
"both kubelet log-query settings"
] | [
"node log query was unconditionally enabled for every Kubernetes 1.30 node"
] | 3e2f1cd44a8e48cd134ba3e0906ab78f002b83e865f085f053cbc2e38f846c61 | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubernetes_130.md"
] | [
{
"acceptable_paraphrases": [
"Node log query was beta in Kubernetes 1.30 but still required the feature gate and both kubelet log-query settings to be enabled.",
"beta in Kubernetes 1.30 / feature gate / both kubelet log-query settings"
],
"canonical_claim": "Node log query was beta in Kube... | The claim "node log query was unconditionally enabled for every Kubernetes 1.30 node" is being checked against the Kubernetes 1.30 record. What does the source support instead regarding maturity and activation requirements? | maturity; activation requirements | [
"kubernetes_130"
] |
[
{
"evidence_refs": [
{
"anchor": "The nftables kube-proxy backend was beta and enabled by default in Kubernetes 1.31, but it required Linux kernel 5.13 or later and could be incompatible with some network plugins.",
"end_line": 15,
"path": "fixtures/answer_ready_confirmatory_transf... | The nftables kube-proxy backend was beta and enabled by default in Kubernetes 1.31, but it required Linux kernel 5.13 or later and could be incompatible with some network plugins. | {
"answer_value_leakage": false,
"authoring_origin": "answer_ready_confirmatory_transfer_150_v1",
"confirmatory_evidence": true,
"development_only": false,
"difficulty": "hard",
"explicit_subject_and_relation": true,
"minimum_source_count": 1,
"requested_slots": [
"maturity/default",
"kernel req... | confirmatory_contradiction_stale_info_006 | contradiction_stale_info | [
{
"anchor": "The nftables kube-proxy backend was beta and enabled by default in Kubernetes 1.31, but it required Linux kernel 5.13 or later and could be incompatible with some network plugins.",
"end_line": 15,
"path": "fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubern... | [
"beta and enabled by default",
"Linux kernel 5.13 or later",
"incompatible with some network plugins"
] | [
"the Kubernetes 1.31 nftables backend worked on every operating system and network plugin"
] | 27de41d1ba1e86666cbec3f01fc4befbb6537594756d15699cbbbbe308cd8765 | [
"fixtures/answer_ready_confirmatory_transfer_v1/software_release_documentation/kubernetes_131.md"
] | [
{
"acceptable_paraphrases": [
"The nftables kube-proxy backend was beta and enabled by default in Kubernetes 1.31, but it required Linux kernel 5.13 or later and could be incompatible with some network plugins.",
"beta and enabled by default / Linux kernel 5.13 or later / incompatible with some netw... | The claim "the Kubernetes 1.31 nftables backend worked on every operating system and network plugin" is being checked against the Kubernetes 1.31 record. What does the source support instead regarding maturity/default, kernel requirement and compatibility limitation? | maturity/default; kernel requirement; compatibility limitation | [
"kubernetes_131"
] |
End of preview.
Sheldon Benchmark
Evaluation suites and frozen results from Sheldon, a study of what makes small, on-device language models (1–4B parameters) accurate on a recurring domain.
The headline finding: under matched, byte-identical contexts, adapting the reader with a completion-only LoRA moved semantic accuracy +38.17 points (53.00% → 91.17% across the 3–4B cohort), while specialized context construction moved it +0.50 points with a confidence interval spanning zero. Everything ran locally on a 16 GB MacBook Air.
Full write-up: https://www.omisaur.app/papers/sheldon
What's here
data/ — evaluation suites (JSONL)
Each row is a question with expected_terms and atomic answer_units used for
proposition-level scoring. Suites:
| File | Cases | Role |
|---|---|---|
scientific_evidence_evolution_final_150.jsonl |
150 | primary frozen benchmark |
answer_ready_confirmatory_transfer_150_v1.jsonl |
150 | confirmatory transfer |
paper_grade_untouched_transfer_150_v1.jsonl |
150 | untouched transfer |
out_of_domain_transfer_150.jsonl |
150 | out-of-domain transfer |
second_out_of_domain_transfer_150.jsonl |
150 | second out-of-domain |
second_out_of_domain_transfer_150_v2.jsonl |
150 | second out-of-domain (v2) |
public_paper_reading.jsonl |
— | public paper-reading probes |
public_pdf_paper_reading.jsonl |
— | public PDF paper-reading probes |
public_pdf_memory_systems.jsonl |
— | memory-systems reading probes |
public_memory_multi_paper_comparison.jsonl |
— | multi-paper comparison |
public_agent_memory_practitioner.jsonl |
— | agent-memory practitioner probes |
results/
benchmark_report.md— the sealed benchmark report; every number in the write-up regenerates from hash-verified outputs.RELEASE_MANIFEST.json— SHA-256 identities for the frozen artifacts.REPRODUCIBILITY.md— how to reproduce the run.
Scoring
Answers are scored against atomic required propositions (answer_units) by a
method- and model-blinded evaluator. Every corpus row, context, output, and judgment
carries a SHA-256 identity; scores open only after all judgments close.
Citation
Bhojane, O. (2026). Sheldon: how model adaptation took a local model from 53% to 91%.
omisaur.app.
License
MIT.
- Downloads last month
- 56