3) a URL to the CC-BY 4.0 license page was used as an object for dct:license, where adopting a CC-By open license further promotes data sharing and reuse and aligns with the FAIR subprinciple R1.1; 4) objects for predicates dcat:landingPage, dcat:accessURL, and dcat:downloadURL are URLs to the online pages describing the dataset made availabe as GitHub pages, the SPARQL endpoint hosting the NanoLinks-KG knowledge graph, and the download link of the RDF dump hosted on Zenodo, respectively. Thus, providing those three predicates, while actually having the linked resources available online, promotes accessibility and aligns with the FAIR subprinciple A1.1. Finally, a namespace called "nanolinks" was reserved on w3id.org and used as a prefix () for all RDF resources described in NanoLinks-KG RDF, giving each and every resource a globally unique identifier which is also resolvable to the corresponding URL on the SPARQL endpoint hosting the knowledge graph. The overall design of the RDF model ensures it follows the linked data design principles , namely: 1) Using Uniform Resource Identifiers (URIs) to assign unique identities to entities, 2) Using HTTP-based URIs to allow software agents to reference and retrieve information about these entities, 3) Expressing entities in RDF format and offering a SPARQL endpoint for querying and accessing data, 4) Including links to external URIs to promote broader knowledge discovery and integration. The process of RDF mapping is depicted in Figure , showing the different components involved in transforming data elements from a source CSV file into RDF. The YARRRML snippet (file: material.yml) in the figure (middle left) shows a part of the rules for nanomaterials representation. Subjects of nanomaterial entities are generated by concatenating a URI prefix ( ) with a hash string of the dataset URL and the nanomaterial ID which is obtained from the relevant column in the data source (CSV file) through a row iterator (highlighted in yellow in Figure ). As stated in methods, custom functions were developed using Java and made available to the RML-Mapper through semantic descriptions using the Function Ontology (FnO) . The source of the Java utility is available on GitHub with online documentation and archived on Zenodo with DOI . One fundamental function is grel:mapToIri (dark green highlight in Figure ) which performs a lookup of the ontology annotation corresponding to a string from a specific group (e.g. nanomaterials, cell lines, assay, unit).