Figure 1
Map highlighting Portugal with a detailed inset of the Pavia region, situated within Mora in the Alentejo area.
Table 1
Description of reference, approach and focus of each research that used as schema model the CIDOC-CRM definition, specifically targeting immovable archaeological heritage.
| REFERENCE | FOCUS |
|---|---|
| Hansen & Fernie (2010) | Describes CARARE metadata schema. The schema focuses on the record of detailed description of heritage, events, and online digital resources. |
| Carlisle et al. (2014) | Documents and share the experience and benefits to incorporate CIDOC-CRM standards into the design of Arches an open source software platform, geospatial information system for heritage inventory and management. |
| Ronzino et al. (2016) | Presents CRMba an extension of CRM to encode metadata about the documentation of archaeological buildings. |
| Gergatsoulis et al. (2021) | Uses CRM and CRMba to represent archaeological buildings derived from fieldwork (records, their provenance and images). |
| Santos et al. (2022) | Uses CRM to represent megalithic monuments – focusing on the megalithic concepts at a granular structural level. |
| Garozzo et al. (2017) | Presents a Cultural Heritage Tool based on Ontology (CulTO) for supporting the modeling of cultural heritage buildings (religious historical building) to develop high-level applications for data curation, retrieval and classification. |
| Garozzo et al. (2021) | Presents an automated hybrid approach (DL-KB) to automatically classify and retrieve photo data. The ontology (CulTO) was used to guide the process of generating synthetic images (GAN: Generative Adversarial Networks) and thus train the DL system. |
Table 2
Overview of the Representation Framework for Dolmens and their Components. The table delineates the structural categorization of the dolmen, the related vocabulary sources consulted for standardization, and specific attributes characterizing each structure.
| WHAT AND HOW TO REPRESENT: THE OBJECT AND ITS COMPONENTS | |||
|---|---|---|---|
| OBJECT STRUCTURE | STRUCTURE INFORMATION | ||
| WHOLE | VOCABULARY DATA SOURCE | WHOLE | DATA SOURCE |
| Dolmen | ROSSIO/GETTY (AAT) | Condition State; Material; Dimension; | Features of the object structure that help to recognise dolmens (Câmara & Batista 2017) |
| COMPONENTS | VOCABULARY DATA SOURCE | COMPONENTS | |
| Chamber | FISH; GETTY (AAT) and Bib (Santos et al. 2022) | Shape Condition State Dimension Orthostat – (number and position) capstone (condition state) | |
| Corridor | Bib (Santos et al. 2022) | Condition State Dimension Orthostat (Number and side) | |
| Burial Mound | ROSSIO | Material Condition State Dimension | |
Figure 2
Knowledge Graph Schema Illustration. Nodes are labeled with CRM entities, interconnected by CRM properties. Blue circles represent nodes containing data source information, yellow indicates monument designation connected to the dolmen representation node and red highlights nodes with unique identifiers.
Figure 3
Analyses of the 73 records from PA in the KG reveals that 46 dolmens were not marked as having their chamber destroyed and were within 1 km of another monument. These dolmens had an average distance of 204 meters to the nearest monument and an average chamber diameter of 2.47 meters. The figure delineates the monuments by conservation status, highlighting average chamber diameters and distances to neighbouring monuments.
Figure 4
Here, we can visualise information about the same monument (Lapeira 1) based on two different sources. There are nodes in dark green representing the monument and its components, and light green nodes (E22) representing the objects in the construction (E19). Yellow nodes describe the structure’s information. The orange nodes represent the data sources (E13, E31, E52). A global ID (E42) is represented by a red node. Nodes in grey define components when no specific entity has been identified (E55).
Table 3
This table describes the main CIDOC-CRM classes used to label KG nodes and their information.
| CLASSES | DESCRIPTION |
|---|---|
| E22 Human-Made Object | This class was used to represent both the dolmen as a whole and its specific components. Discrete used or processed pieces, such as the components from a dolmen, were modelled as parts (chamber, corridor, and burial mound). To relate the dolmen with these components, the P46 is composed of (forms part of) was used, thus creating a hierarchical relation of parts (E22: P46: E22). |
| E19 Physical Object | This class was used to represent the physical objects used to build each component of the Human-Made Object (e.g. orthostats), forming a (E22: P46: E19) relation. |
| E16 Measurement | This class was used to describe, either in terms of the whole, or in terms of each component of the dolmen, the actions taken to measure the object. In order to represent it, the E22 instances corresponding to the dolmen are related to the E16 entity by a P39 measured (was measured by) (E22: P39: E16) relation. |
| E54 Dimension | This class was used to define a value of the element measured. The P40 observed dimension (was observed in) relates the action of measuring an object with the obtained value: (E16: P40: E54). |
| E58 Measurement Unit | This class was used to define a measurement unit of the dimension being indicated, thus the relationship between them is defined by the property P91 has unit (is unit of) (E54: P91: E58). |
| E60 Number | This class was used to identify the number of elements represented as instances of E19, thus the relationship between them is defined by the property P57 has number of parts (E19: P57: E60). |
| E57 Material | This class was used to identify the materials used to build the dolmen components represented as instances of E22, thus the relationship between them is defined by the property P45 consists of (is incorporated in) (E22: P45: E57). |
| E3 Condition State | This class was used to identify the the state of the components represented as instances of E22, thus the relationship between them is defined by the property P44 has condition (is condition of) (E22: P44: E3). |
| E55 Type | This class was used to define concepts and to determine whether it was possible to represent the monuments structure composition only by using the CIDOC-CRM classes and properties. The class E55 was used to define the dimension of the object components (e.g., “diameter” – “height”) (E58: P2: E55), the document of the time span (e.g. “data source date”) (E52: P2: E55), the cardinal directions of the orthostats (e.g “left”, “right”) (E60: P2: E55) and the monument type (“Dolmen”) (E22: P2: E55). In all cases the relation is made thrpugh the property P2 has type (is type of). |
| E42 Identifier | This class was used to attribute an unique ID (Global ID) for each dolmen represented as an instance of E22, thus the relationship between them is defined by the property P48 has preferred identifier (is preferred identifier of) (E22: P48: E42). |
| E13 Attribute Assignment | This class was used to represent action of describing the dolmen’s attributes to the dolmen described – acting as a bridge between the data source and the E22. Thus the relationship between them is defined by the property P140 assigned attribute to (was attributed by) (E13: P140: E22). |
| E31 Document | This class was used to represent the data source from which propositions about the object were gathered (e.g., Archaeologist’s Portal or Carta Arqueológica de Mora) – resulted of describing the dolmen represented as an instance of E13. Thus the relationship between them is defined by the property P70 documents property (is documented in) (E13: P70: E31). |
| E52 Time Spam | This class was used to represent two types of data : i.) A record’s date of origin (data source date) when it has a date, and ii.) the date when the data was acquired and inserted into the KG, thus this class is related to the E13 thought the property P4 has time-span (is a time-span of) (E2: P4: E52). The class E55 Type (previously described) defines date types. |
| E41 Appellation | This class was used to represent the denomination(s) of the dolmen represented as an instance of E22, thus the relationship between them is defined by the property P1 is identified by (identifies) (E22: P1: E41). |