PCI Archaeology

338

Title *

Transforming the CIDOC-CRM model into a megalithic monument property graphuse asterix (*) to get italics

Authors *

Ariele Câmara, Ana de Almeida, João Oliveira Please use the format "First name initials family name" as in "Marie S. Curie, Niels H. D. Bohr, Albert Einstein, John R. R. Tolkien, Donna T. Strickland"

Year *

2024

Picture *

Abstract *

<p>This paper presents a method to store information about megalithic monuments' building components as graph nodes in a knowledge graph (KG). As a case study we analyse the dolmens from the region of Pavia (Portugal). To build the KG, information has been extracted from unstructured data to populate a schema model based on the International Committee for Documentation - Conceptual Reference Model (CIDOC-CRM). In order to prepare the archaeological monument's information for bulk loading, it was transformed into semi-structured data. While the semi-structured file was used to populate the classes with their respective properties and instances, the KG labels and types were defined using some of the entities and relations defined by the CIDOC-CRM. The knowledge-driven model was built to represent dolmens in a formal and structured manner using Neo4J, a property-graph database. Modeling a labeled property graph based on predefined labels as a KG enables to transform textual semantic data into instances and properties. Thus, we show that it is possible to represent at a granular level all the information about the structural components of monuments since heterogeneities, granularities, and large amounts of data can be handled by a KG. Therefore, a KG implemented using a native graph database can improve data storage and processing, making it interoperable either between humans, between humans and machines and machine-to-machine.</p>

Indicate the full web address (DOI or URL) giving public access to these data (if you have any problems with the deposit of your data, please contact contact@archaeo.peercommunityin.org). In case all raw data are included in the preprint, indicate the DOI or URL of the preprint. *

You should fill this box only if you chose 'All or part of the results presented in this preprint are based on data'. URL must start with http:// or https://

Indicate the full web address (DOI or URL) giving public access to these scripts (if you have any problems with the deposit of your scripts, please contact contact@archaeo.peercommunityin.org). In case all raw scripts are included in the preprint, indicate the DOI or URL of the preprint. *

You should fill this box only if you chose 'Scripts were used to obtain or analyze the results'. URL must start with http:// or https://

Indicate the full web address (DOI, SWHID or URL) giving public access to these codes (if you have any problems with the deposit of your codes, please contact contact@archaeo.peercommunityin.org). In case all raw codes are included in the preprint, indicate the DOI or URL of the preprint. *

You should fill this box only if you chose 'Codes have been used in this study'. URL must start with http:// or https://

Keywords (optional)

knowledge graph, dolmen, CIDOC-CRM, labeled property graph, Neo4J

Methods that require specific expertise (optional)

NonePlease indicate the methods that may require specialised expertise during the peer review process (use a comma to separate various required expertises).

Thematic fields *

Computational archaeology

Suggested reviewers - Suggest up to 10 reviewers (provide names and Email addresses). (Optional)

Enrique Cerrillo-Cuenca suggested: Ivo Santos, ifs@uevora.pt

e.g. John Doe john@doe.com

No need for them to be recommenders of PCIArchaeology. Please do not suggest reviewers for whom there might be a conflict of interest. Reviewers are not allowed to review preprints written by close colleagues (with whom they have published in the last four years, with whom they have received joint funding in the last four years, or with whom they are currently writing a manuscript, or submitting a grant proposal), or by family members, friends, or anyone for whom bias might affect the nature of the review - see the code of conduct

Opposed reviewers - Suggest up to 5 people not to invite as reviewers. (Optional)

e.g. John Doe john@doe.com

Submission date

2023-05-29 13:46:49

Recommender

Isto Huvila

Reviewers

or Register
Submit a preprint