The dataset viewer is not available for this split.
Error code: FeaturesError
Exception: ArrowTypeError
Message: ("Expected bytes, got a 'list' object", 'Conversion failed for column Access_Control_Configuration_edge_yes_1 with type object')
Traceback: Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/split/first_rows.py", line 244, in compute_first_rows_from_streaming_response
iterable_dataset = iterable_dataset._resolve_features()
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 4408, in _resolve_features
features = _infer_features_from_batch(self.with_format(None)._head())
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2679, in _head
return next(iter(self.iter(batch_size=n)))
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2861, in iter
for key, pa_table in ex_iterable.iter_arrow():
~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2395, in _iter_arrow
yield from self.ex_iterable._iter_arrow()
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 536, in _iter_arrow
for key, pa_table in iterator:
^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 419, in _iter_arrow
for key, pa_table in self.generate_tables_fn(**gen_kwags):
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 168, in _generate_tables
pa_table = pa.Table.from_pandas(df, preserve_index=False)
File "pyarrow/table.pxi", line 4796, in pyarrow.lib.Table.from_pandas
File "/usr/local/lib/python3.14/site-packages/pyarrow/pandas_compat.py", line 651, in dataframe_to_arrays
arrays = [convert_column(c, f)
~~~~~~~~~~~~~~^^^^^^
File "/usr/local/lib/python3.14/site-packages/pyarrow/pandas_compat.py", line 639, in convert_column
raise e
File "/usr/local/lib/python3.14/site-packages/pyarrow/pandas_compat.py", line 633, in convert_column
result = pa.array(col, type=type_, from_pandas=True, safe=safe)
File "pyarrow/array.pxi", line 365, in pyarrow.lib.array
File "pyarrow/array.pxi", line 91, in pyarrow.lib._ndarray_to_array
check_status(NdarrayToArrow(pool, values, mask, from_pandas,
File "pyarrow/error.pxi", line 92, in pyarrow.lib.check_status
raise convert_status(status)
pyarrow.lib.ArrowTypeError: ("Expected bytes, got a 'list' object", 'Conversion failed for column Access_Control_Configuration_edge_yes_1 with type object')Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
license: mit language: - en tags: - Knowledge Graph alignment - Semantic Invariance - Question answering - LLM consistency pretty_name: Cybersecurity data for Semantic Invariance Testing size_categories: - 1M<n<10M
The SI-Cyber dataset is derived from subgraphs extracted from the MITRE D3FEND ontology and contains a total of 5,934 graph edges.
The dataset is organized into 7,980 query clusters. Each cluster tests a specific ontological relation using multiple semantically equivalent formulations. This structure enables systematic evaluation of whether a model produces consistent answers across paraphrases of the same underlying query.
Clusters cover several forms of graph-based reasoning, ranging from direct edge lookup to hierarchical, inverse, and relational reasoning. Each cluster is associated with an expected binary answer (yes or no) determined from the underlying ontology.
Each cluster identifier encodes the source node, cluster type, expected answer, and a unique identifier. The cluster type indicates the graph or logical pattern being tested, such as a direct edge, a transitive path, or an inverse relation.
Each cluster contains:
- the expected answer;
- the source node;
- the relation being tested;
- the target node, not necessarily adjacent in the case of inferred links.
- four paraphrased questions expressing the same underlying query; and
- four corresponding declarative statements.
The example below tests whether Application Configuration Database Record is a subConceptOf Configuration Database Record. Because this relation is supported by the ontology, the expected answer is yes.
{
"Application_Configuration_Database_Record_edge_yes_2": {
"expected_answer": "yes",
"source": "Application Configuration Database Record",
"property": "subConceptOf",
"target": "Configuration Database Record",
"questions": [
"is 'Application Configuration Database Record' a subconcept of 'Configuration Database Record' ?",
"is 'Application Configuration Database Record' a type of 'Configuration Database Record' ?",
"is every kind of 'Application Configuration Database Record Configuration Database Record' also a kind of 'Configuration Database Record' ?",
"is 'Application Configuration Database Record' a subcategory of 'Configuration Database Record' ?"
],
"statements": [
"'Application Configuration Database Record' is a subconcept of 'Configuration Database Record' ",
"'Application Configuration Database Record' is a type of 'Configuration Database Record'",
"every kind of 'Application Configuration Database Record Configuration Database Record' is also a kind of 'Configuration Database Record' ",
"'Application Configuration Database Record' is a subcategory of 'Configuration Database Record' "
]
}
}
The following example illustrates a negative cluster. Here, the ontology does not support the queried subConceptOf relation between Access Modeling and Identifier Activity Analysis, so the expected answer is no. For negative clusters, the corresponding declarative statements express the negated form of the queried relation.
"Access_Modeling_edge_no_1": {
"expected_answer": "no",
"source": "Access Modeling",
"property": "subConceptOf",
"target": "Identifier Activity Analysis",
"questions": [
"is 'Access Modeling' a subconcept of 'Identifier Activity Analysis' ?",
"is 'Access Modeling' a type of 'Identifier Activity Analysis' ?",
"is every kind of 'Access Modeling' also a kind of 'Identifier Activity Analysis' ?",
"is 'Access Modeling' a subcategory of 'Identifier Activity Analysis' ?"
],
"statements": [
"'Access Modeling' is not a subconcept of 'Identifier Activity Analysis' ",
"'Access Modeling' is not a type of 'Identifier Activity Analysis'",
"not every kind of 'Access Modeling' is also a kind of 'Identifier Activity Analysis' ",
"'Access Modeling' is not a subcategory of 'Identifier Activity Analysis' "
]
}
- Downloads last month
- 65