# Representing and Validating Cultural Heritage Knowledge Graphs in CIDOC-CRM Ontology
## 3 Aligning COURAGE Entities to the CIDOC CRM Ontology
### Mapping of Properties to CIDOC-CRM  
As the third step of the mapping process is the mapping of properties, the equivalent properties have been defined. These properties are listed in Table 1, Table 2, Table 3, and Table 4. Although mapping COURAGE properties to the CIDOC-CRM ontology was straightforward for some properties, in other cases it required analytical study to decide the best representation in CIDOC-CRM. \begin{table}
\begin{tabular}{l l l} \hline \hline
**Courage** & **CIDOC-CRM Entity** & **CIDOC-CRM Property** \\ \hline Given name & E82 Actor Appellation & P131 is identified by \\ Family name & E82 Actor Appellation & P131 is identified by \\ Label & E35 Title & P1 is identified by \\ Leader of & E85 Joining & P143 joined \\ Birthplace & E67 Birth & P7 took place at \\ Birthdate & E67 Birth & P98 brought into life \\ Profession & E55.1 Profession & P2 has type \\ Educational background & E55.2 Educational & P2 has type \\  & Background & P107 has current/former \\ Main member of & E74 Group & member \\ Creator of & E12 Production & P14 carried out by \\ Main actor of & E5 Event & P11 had participant \\ Founder & E63 Beginning of Existence & P11.had participant \\ Owner roles & E8 Acquisition & P22 transferred title to \\ Creator roles & E87 Curation Activity & P14 carried out by \\ Operator roles & E87 Curation Activity & P14 carried out by \\ Colllectorships & E87 Curation Activity & P14 carried out by \\ Stakeholder roles & E87 Curation Activity & P14 carried out by \\ Supporter roles & E87 Curation Activity & P14 carried out by \\ \hline \hline \end{tabular}
\end{table} 
Table 1: COURAGE person entity representation in CIDOC-CRM. The first decision happened regarding the expression of primitives, especially the time intervals of E52 time-span instances. In CIDOC CRM versions prior to 6 [21], there were P82a and P82b properties to denote the beginning and end of a time span. Contrary to paper [12], where they used the \"P78_is_identified_by\" property for time spans. We have chosen the use of P82a and P82b properties, so these two properties were added to the used version of the CIDOC CRM ontology. The benefit of applying these properties is that they can be used uniformly with both curation activities and birth and death events. Entities of the COURAGE knowledge base have URIs ending in a unique and opaque identifier in the form of nxxxx (where x stands for numbers). These URIs can be seen in the following figures, such as courage:n1014. Another representation question was about names. The simplest and often used solution is to use the rdfs:label property to assign a name to an entity. The E41_Appellation class may be utilized instead of rdfs:label when there is a need to assign properties to the E41_Appellation [22]. As exemplified in Figure 4, E82_Actor_Appellation was used to represent the names of person and organization entities in order to prevent repeated names. \begin{table}
\begin{tabular}{l l l} \hline \hline
**Courage** & **CIDOC-CRM Entity** & **CIDOC-CRM Property** \\ \hline masterpieceOf & E79 Part Addition & P111 added \\ masterpiece\_type & E55.7 Item Type & P2 has type \\ hasItemTopic & E55.6 Topic & P2 has type \\ \hline \hline \end{tabular}
\end{table} 
Table 4: COURAGE featured item entity representation in CIDOC-CRM. \begin{table}
\begin{tabular}{l l l} \hline \hline
**Courage** & **CIDOC-CRM Entity** & **CIDOC-CRM Property** \\ \hline \hline \multirow{2}{*}{
\begin{tabular}{l} InsOperationalType \\ yearOfFunding \\ instType \\ \end{tabular} } & E55.3 Operational Type & P2 has type \\  & E66 Formation & P95 has formed \\  & E55.4 Organisational Type & P2 has type \\ \hline \hline \end{tabular}
\end{table} 
Table 2: COURAGE organization entity representation in CIDOC-CRM.