1) Search and filter the data of the Work URIs and their identifier-properties in the Series-level of the Chinese Rare Books Database.
2) Search and filter the data of the Work URIs and their identifier-properties in the Monograph-level of the Chinese Rare Books Database.
3) Search and filter the data of the Work URIs and their identifier-properties in the Volume-level of the Chinese Rare Books Database.
4) Count the numbers by the level types as the Series, Monographs and Volumes.

1) Search the data values of Sibu-Classification, by using the property as ascdc:FSNLibraryClassHeading1, of all books in the Chinese Rare Books Database.
2) Count the numbers by different types of Sibu-Classification.

1) Search the data values of institutional repositories, by using the property as bf:heldBy, of all books in the Chinese Rare Books Database.
2) Count the numbers by different types of institutional repositories.

1) Search and list all the properties applied in the dataset.
2) Count the numbers by different property types.

Released soon

1) In the Database of Chinese Rare Books, set S as Book_Work URIs, set P as skos:prefLabel to search all the book titles as value O.
2) Set S as the Book_Work URIs from step 1, query those monograph Book_Work URIs containing the data field P of ascdc:FSNLibraryClassHeading1 with their data values.
3) Set S as the Book_Work URIs from step 1, query those monograph Book_Work URIs containing the data field P of ascdc:FSNLibraryClassHeading2 with their data values.
4) Display the results by BookWork URI, Label, Sibu_Classification1, Sibu_Classification2.

1) In the Database of Chinese Rare Books, set S as Book_Work URIs, set P as skos:prefLabel to search all the book titles as value O.
2) Set S as the Book_Work URIs from step 1, query those monograph Book_Work URIs containing the data field P of bf:hasInstance with monograph Book_Instance URIs.
3) Set S as the Book_Instance URIs from step 2, query those Book_Instance URIs containing the data field P of dbpedia-owl:dynasty.
4) Display the results by BookWork URI, Label, Dynasty.

1) In the Database of Chinese Rare Books, set S as Book_Work URIs, set P as skos:prefLabel to search all the book titles as value O.
2) Set S as the Book_Work URIs from step 1, query those monograph Book_Work URIs containing the data field P of bf:hasInstance with monograph Book_Instance URIs.
3) Set S as the Book_Instance URIs from step 2, query those Book_Instance URIs containing the data field P of dbpedia-owl:era.
4) Display the results by BookWork URI, Label, Era.

1) In the Database of Chinese Rare Books, set S as Book_Work URIs, set P as skos:prefLabel to search all the book titles as value O.
2) Set S as the Book_Work URIs from step 1, query those monograph Book_Work URIs containing the data field P of bf:hasInstance with monograph Book_Instance URIs.
3) Set S as the Book_Instance URIs from step 2, query those Book_Instance URIs containing the data field P of owl:versionInfo.
4) Display the results by BookWork URI, Label, VersionType.

1) In the Database of Chinese Rare Books, set S as Book_Work URIs, set P as skos:prefLabel to search al the book titles as value O.
2) Set S as the Book_Work URIs from step 1, query those monograph Book_Work URIs containing the data field P of bf:hasInstance with monograph Book_Instance URIs.
3) Set S as the Book_Instance URIs from step 2, query those Book_Instance URIs containing the data field P of bf:originPlace and rdfs:label with value of Place.
4) Set S as the Book_Instance URIs from step 3, query those Book_Instance URIs containing the data field P of owl:versionInfo with value of “Printed Version” (刊本).
5) Display the results by Work URI, Label, Instance URI, Place, Version.

1) Set all the data with the value S as Work URI and P as skos:prefLabel.
2) Retain the value S and set the value P as bf:title and O as VariantTitle URI. Then set the value S as VariantTitle URI, the value P as bf:variantType and rdfs:label, and the value O for the type of variant titles and strings of those variant titles.
3) Display the results by Work URI, Title, Varinat Title, Type of Variant Title.

1) Set the values of property as skos:prefLabel and their Instance URIs. Then set the Instance URI as S and the value O as the URI of Contribution by using bf:contribution.
2) Set the value S as Contribution URI, the value P as bf:agent and bf:role, and the value O as label of bf:agent and bf:role.
3) Order the sesults by Work URI, Title, Agent URI, Agent Name, Role URI and Role Type of the contributors.

1) For records in the LOD Database of Chinese Rare Books, set S as the Book_Work URIs, set the data field P as bf:hasInsatnce and set O as the Book_Instance URIs.
2) Set S as the Book_Work URIs from step 1, then query the data field P for those with O values of skos:prefLabel.
3) Set S as the Book_Work URIs from step 2, then query the data field P for those with O values of ascdc:FSNLibraryClassHeading1.
4) Set S as the Book_Instance URIs from step 1, then query the data field P of dbpedia-owl:era for those with O values of “Era of Publication.”
5) Set S as the Book_Instance URIs from step 1, then query the data field P of bf:date for those with O values of “Year of Publication” URIs.
6) Set S as the Year of Publication URIs from step 5, then query the data field P for those with O values of rdfs:label. Use“FILTER”to limit query results to those with "Year Names" labeled as Tianqi (天啟), Chongzhen (崇禎), Shunzi (順治), Kangxi (康熙), or Yongzheng (雍正).
7) Order results by Work, Title, Era, Year and Sibu-Classification.

1) In the LOD Dataset of Names and Biographies, find values of O, which has P as gndo:publication. Suppose this queried information as series (a). In the LOD Dataset of the Chinese Rare Books, set every S value as work URI, the P value as the O value of skos:prefLabel i.e. the title of books. Suppose this set of information as series (b). Compare (a) and (b). The overlap between (a) and (b) contains the title of publications and work URI in the LOD Dataset of the Chinese Rare Books.
2) Search person's name in the Database of Names and Biographies, which meet the query condition as mentioned in the step 1, by using the property as skos:prefLabel.
3) Display the Work URI and main title of publications listed in both the Dataset of the Chinese Rare Books and Person's URI of the Database of Names and Biographies and person name.

1) For records in the LOD Database of Chinese Rare Books, search data values of the property as skos:prefeLabel of all Work URIs.
2) Set S as the Work URIs from step 1, then query the data field P of bf:hasInstance and set O as the Instance URIs.
3) Set S as the Instance URIs from step 2, then query the data field P of bf:editionStatement and set those values as O.
4) Order results by Work, Title and Edition_Statement.

1) For records in the LOD Database of Chinese Rare Books, set S as the Part Instance URIs that contain the property values in the data field of the "lines per page" (行款).
2) Set S as the Part_Instance URIs from step 1, then query the data field P of bf:partOf and set O as the Book_Instance URIs.
3) Set O as the Book_Instance URIs from step 2, then query the data field P of bf:hasInstance and set S as the monograph Book_Work URIs.
4) Set S as the Book_Instance URIs from step 3, then query the data field P for those O values of skos:prefLabel.
5) Order results by BookWork, Label, LinesPerPage.

1) For records in the LOD Database of Chinese Rare Books, set S as the Part_Instance URIs that contain the property values in the data field of the “type of framing line” (邊欄).
2) Set S as the Part_Instance URIs from step 1, then query the data field P of bf:partOf and set O as the Book_Instance URIs.
3) Set O as the Book_Instance URIs from step 3, then query the data field P of bf:hasInstance and set S as the Book_Work URIs.
4) Set S as the Book_Work URIs from step 5, then query the data field P of skos:prefLabel and set those values as O.
5) Order results by Instance BookWork, Label, FramengLineType.

1) For records in the LOD Database of Chinese Rare Books, set S as the Part_Instance URIs that contain the property values in the data field of “YuWei pattern” (魚尾).
2) Set S as the Part_Instance URIs from step 1, then query the data field P of bf:partOf and set O as the Book_Instance URIs.
3) Set O as the Book_Instance URIs from step 2, then query the data field P of bf:hasInstance and set S as the Book_Work URIs.
4) Set S as the Book_Work URIs from step 4, then query the data field P of skos:prefLabel and set those values as O.
5) Order results by BookWork, Label and YuWei.

1) Locate every Work URI in the level of monographies, which contains value as 方志 (local history chrpnicles) in data field of bf:subject.
2) Look for the content in the field of ascdc:FSNLibraryClassHeading in the Work URIs obtained in step 1.
3) Look for the Work URI of the Library of Congress (LC) in the field of owl:sameAs in the Work URIs obtained in step 1.
4) Look for the URI in the field of bf:subject of the LC Work URIs obtained in step 3.
5) Look for the value in the field of rdfs:label in the URI as obtained in step 4.
6) Order results by CRB Work, CRB Subject, LC Work, LC Subject.

1) Locate every Work URI in the level of monographies, which contains value as 嘉興府志 (Jiaxingfuzhi) in data field of skos:prefLabel.
2) Select the Works URI beginning with "http://data.ascdc.tw/Book/crb/Book_Work/" from the results queried in the step 1.
3) Look for the Instance URI in the field of bf:hasInstance from the Work URIs obtained in step 2.
4) Look for the value in the field of bf:editionStatement in the Instance URI obtained in step 3.
5) Look for the LC Work URI in the field of owl:sameAs and rdfs:seeAlso in the Work URI obtained in step 2.
6) Look for the LC Instance URIs in the field of bf:hasInstance from the LC Work URI obtained in step 5.
7) Look for the values marked with language type as @zh-hani in the field of bf:editionStatement in the LC Instance URIs obtained in step 6.
8) Order results by CRB Work, CRB Label, CRB Edition, LC Work, LC Edition.

1) For records in the LOD Database of Chinese Rare Books, set S as the Monograph Work URIs, set the Sibu-classification (四部分類) data field P as bf:subject, and set O as “春秋”(Chunqiu).
2) Set S as the Book_Work URIs from step 1, then query those monograph Book_Work URIs containing the data field P of skos:prefLabel with value of monograph's Label.
3) Set S as the Book_Work URIs from step 2, then query those monograph Book_Work URIs containing the data field P of bf:hasInstance with monograph Book_Instance URIs.
4) Set S as the Book_Instance URIs from step 3, then query those monograph Book_Instance URIs containing the data field P of dbpedia-owl:dynasty with value of Dynasty.
5) Set S as the Book_Instance URIs from step 4, then query those monograph Book_Instance URIs containing the data field P of dbpedia-owl:era with value of Era.
6) Set S as the Book_Instance URIs from step 5, then query those monograph Book_Instance URIs containing the data field P of owl:versionInfo with value of Version.
7) Order results by Instance BookWork, Label, Sibu, Dynasty, Era, Version.

1) Set the value S as the Instance URI of monographs in question, the value P as bf:date, and the value Era as the URI of regnal year.
2) Display values Era URIs as S and labels of those Era URIs.
3) Look for the sum of every Era value in the column for numbers.

1) Set every value S as "Work" (referring to the single monograph) and the Instance URI, the value P as the value O for bf:contribution and bf:agent to obtain the literal names of people to which the O values correspond.
2) Set the value S as "Work" and the Instance URI of the data fields obtained through step 1 and set the value P as the value O of dcterms:identifier.
3) Set the value S as the Work URI of the data fields obtained through step 1 and the value P as the value O of skos:prefLabel.
4) Display the monographs' URI, titles of label, and names of contributors associated with the volume.

1) For records in the LOD Database of Chinese Rare Books, set S as the Part Instance URIs, set the lines per page (行款) data field P as ascdc:linesPerPage, and set O as “10 lines 20 words” or “ten lines twenty words.”
2) Set S as the Part_Instance URIs from step 1, then query the data field P of bf:partOf and set O as the Book_Instance URIs.
3) Set S as the Book_Instance URIs from step 2, then query those monograph Book_Instance URIs containing the data field P of owl:versionInfo with the value of Edition (刊本).
4) Set S as the Book_Instance URIs from step 3, then query those monograph Book_Instance URIs containing the data field P of dbpedia-owl:era and dbpedia-owl:dynasty.
5) Set O as the Book_Instance URIs from step 4, then query the data field P of bf:hasInstance and set S as the monograph Book_Work URIs.
6) Set S as the Book_Instance URIs from step 5, then query the data field P for those with O values of ascdc:FSNLibraryClassHeading1 and ascdc:FSNLibraryClassHeading2.
7) Set S as the Book_Instance URIs from step 6, then query the data field P for those O values of skos:prefLabel.
8) Order results by BookWork, LinesPerPage, Label, Version, Dynasty, Era, Subject1 and Subject2.

1) For records in the LOD Database of Chinese Rare Books, set S as the Part_Instance URIs that contain both the “margin line” (邊欄) data field P set as ascdc:framelineType with the value of “double-framed margin line” (雙欄), and the “YuWei pattern” (魚尾) data field P set as ascdc:yuWei with the value of “double YuWei pattern” (雙魚尾).
2) Set S as the Part_Instance URIs from step 1, then query the data field P of bf:partOf and set O as the Book_Instance URIs.
3) Set S as the Book_Instance URIs from step 2, then query the “dynasty” data field P of dpedia-owl:dynasty and set those values as O.
4) Set O as the Book_Instance URIs from step 3, then query the data field P of bf:hasInstance and set S as the Book_Work URIs.
5) Set S as the Book_Work URIs from step 4, then query the data field P of ascdc:FSNLibraryClassHeading1 and set those values as O.
6) Set S as the Book_Work URIs from step 5, then query the data field P of skos:prefLabel and set those values as O.
7) Order results by Instance BookWork, Label, FrameLineType, Subject, YuWei, and DynastyLabel.

This is a template of "What was the first position of whom had been a "OOO" in the Qing dynasty?". (Default option of "OOO" is "總督".)
"OOO" can be filled with any other title of office from the following databse:" http://archive.ihp.sinica.edu.tw/officerc/officerkm2?"

How to use:
Freely enter the title of office you picked (full name or key words in Chinese) in the ’ ’ at line 9 of "Query examples" area, such as ’安徽巡撫’ and ’布政使’. Then click the submit buttom to get your own result.

Result (Triples):
1. "name": Names of officers correspand to the requirements in this question from the DNB LOD-based dataset.
"Position": Titles of office of whom are correspand to the requirements in this question.
"First Position(DNB)": The first title of office in career of whom are correspand to the requirements in this question.(Records from DNB LOD-based dataset)
"First Position(DQOT)": The first title of office in career of whom are correspand to the requirements in this question.(Records linked to DQOT LOD-based dataset)
2. There are 4 formats for downloading: JSON, XML, TTL, CSV. CSV files can be opened with Microsoft® Office Excel.
3. The formal names of some titles are identical to the others’ alias, so they are both shown in the result.

*DNB LOD-based dataset: Database of Names and Biographies LOD-based dataset
*DQOT LOD-based dataset: Database of Qing Official Titles LOD-based dataset

This is a template of "Was the order "OOO"→"OOO" →"OOO" a common career path in the Qing dynasty?". (Default options of "OOO" are "按察使", "布政使", and "巡撫".)
"OOO" can be filled with any other title of office from the following databse:" http://archive.ihp.sinica.edu.tw/officerc/officerkm2?"

How to use:
Freely enter the title of office you picked (full name or key words in Chinese) in the ’ ’ at line 12 of "Query examples" area, such as ’安徽巡撫’ and ’布政使’. Then click the submit buttom to get your own result.

Result (Triples):
1. "Name": Names of officers correspand to the requirements in this question from the DNB LOD-based dataset.
"Position 1": The first title of office of whom are correspand to the requirements in this question.
"Position 2": The second title of office of whom are correspand to the requirements in this question.
"Position 3": The third title of office in career of whom are correspand to the requirements in this question.
(The numbers 1,2,3 just represent the order of titles in the specific path.)
2. There are 4 formats for downloading: JSON, XML, TTL, CSV. CSV files can be opened with Microsoft® Office Excel.
3. The formal names of some titles are identical to the others’ alias, so they are both shown in the result.

*DNB LOD-based dataset: Database of Names and Biographies LOD-based dataset

This is a template of "How many bannermen (qiren) and civilians (minren) were there respectively of whom had been a "OOO" in the Qing dynasty?". (Default option of "OOO" is "巡撫".)
"OOO" can be filled with any other title of office from the following databse:" http://archive.ihp.sinica.edu.tw/officerc/officerkm2?"

How to use:
Freely enter the title of office you picked (full name or key words in Chinese) in the ’ ’ at line 9 of "Query examples" area, such as ’安徽巡撫’ and ’布政使’. Then click the submit buttom to get your own result.

Result (Triples):
1. "Name": Names of officers correspand to the requirements in this question from the DNB LOD-based dataset.
"Position": Titles of office of whom are correspand to the requirements in this question.
"EightBanners": The records of Eight Banners of whom are correspand to the requirements in this question. (Blank：civilians (minren) )
2. There are 4 formats for downloading: JSON, XML, TTL, CSV. CSV files can be opened with Microsoft® Office Excel.
3. The formal names of some titles are identical to the others’ alias, so they are both shown in the result.

*DNB LOD-based dataset: Database of Names and Biographies LOD-based dataset

This is a template of "How many bannermen (qiren) belonged to "XX" ,and also were a "OOO" in the Qing dynasty?". (Default option of "XX" is "漢軍", and "OOO" is "巡撫".)
"OOO" can be filled with any other title of office from the following databse:" http://archive.ihp.sinica.edu.tw/officerc/officerkm2?"

How to use:
Freely enter the value you want (full name or key words in Chinese) in the ’ ’ at line 10 and line 11 of "Query examples" area, such as ’安徽巡撫’ , ’布政使’, ’滿洲’ , and ’正紅旗’. Then click the submit buttom to get your own result.

Result (Triples):
1. "Name": Names of officers correspand to the requirements in this question from the DNB LOD-based dataset.
"Position": Titles of office of whom are correspand to the requirements in this question.
"EightBanners": The records of Eight Banners of whom are correspand to the requirements in this question.
2. There are 4 formats for downloading: JSON, XML, TTL, CSV. CSV files can be opened with Microsoft® Office Excel.
3. The formal names of some titles are identical to the others’ alias, so they are both shown in the result.

*DNB LOD-based dataset: Database of Names and Biographies LOD-based dataset

This is a template of "What were the imperal examination results of whom had been a "OOO" in the Qing dynasty?". (Default option of "OOO" is "巡撫".)
"OOO" can be filled with any other title of office from the following databse:" http://archive.ihp.sinica.edu.tw/officerc/officerkm2?"

How to use:
Freely enter the title of office you picked (full name or key words in Chinese) in the ’ ’ at line 10 of "Query examples" area, such as ’安徽巡撫’ and ’布政使’. Then click the submit buttom to get your own result.

Result (Triples):
1. "Name": Names of officers correspand to the requirements in this question from the DNB LOD-based dataset.
"Position": Titles of office of whom are correspand to the requirements in this question.
"ImperialExamination": The resords of imperial examination of whom are correspand to the requirements in this question.
2. There are 4 formats for downloading: JSON, XML, TTL, CSV. CSV files can be opened with Microsoft® Office Excel.
3. The formal names of some titles are identical to the others’ alias, so they are both shown in the result.

*DNB LOD-based dataset: Database of Names and Biographies LOD-based dataset

This is a template of "What were the specialties of whom had been a "OOO" in the Qing dynasty?". (Default option of "OOO" is "巡撫".)
"OOO" can be filled with any other title of office from the following databse:" http://archive.ihp.sinica.edu.tw/officerc/officerkm2?"

How to use:
Freely enter the title of office you picked (full name or key words in Chinese) in the ’ ’ at line 11 of "Query examples" area, such as ’安徽巡撫’ and ’布政使’. Then click the submit buttom to get your own result.

Result (Triples):
1. "Name": Names of officers correspand to the requirements in this question from the DNB LOD-based dataset.
"Position": Titles of office of whom are correspand to the requirements in this question.
"Specialty": The resords of specialty of whom are correspand to the requirements in this question. (Some records are linked to Art & Architecture Thesaurus Online, AAT )
2. There are 4 formats for downloading: JSON, XML, TTL, CSV. CSV files can be opened with Microsoft® Office Excel.
3. The formal names of some titles are identical to the others’ alias, so they are both shown in the result.

*DNB LOD-based dataset: Database of Names and Biographies LOD-based dataset

This is a template of "Where were the nativeplaces of whom had been a "OOO" in the Qing dynasty?". (Default option of "OOO" is "巡撫".)
"OOO" can be filled with any other title of office from the following databse:" http://archive.ihp.sinica.edu.tw/officerc/officerkm2?"

How to use:
Freely enter the title of office you picked (full name or key words in Chinese) in the ’ ’ at line 11 of "Query examples" area, such as ’安徽巡撫’ and ’布政使’. Then click the submit buttom to get your own result.

Result (Triples):
1. "Name": Names of officers correspand to the requirements in this question from the DNB LOD-based dataset.
"Position": Titles of office of whom are correspand to the requirements in this question.
"NativePlace": The resords of native place of whom are correspand to the requirements in this question.
"TGAZ API": Records of native placename linked to "Temporal Gazetteer API, The China Historical Geographic Information System".
2. There are 4 formats for downloading: JSON, XML, TTL, CSV. CSV files can be opened with Microsoft® Office Excel.
3. The formal names of some titles are identical to the others’ alias, so they are both shown in the result.

*DNB LOD-based dataset: Database of Names and Biographies LOD-based dataset

This is a template of "In the Qing dynasty, who were the fathers, ancestors, and friends of whom had been a "OOO" ?". (Default option of "OOO" is "巡撫".)
"OOO" can be filled with any other title of office from the following databse:" http://archive.ihp.sinica.edu.tw/officerc/officerkm2?"

How to use:
Freely enter the title of office you picked (full name or key words in Chinese) in the ’ ’ at line 11 of "Query examples" area, such as ’安徽巡撫’ and ’布政使’. Then click the submit buttom to get your own result.

Result (Triples):
1. "Name": Names of officers correspand to the requirements in this question from the DNB LOD-based dataset.
"Father": Names of officers’ fathers correspand to the requirements in this question from the DNB LOD-based dataset.
"Ancestors": Names of officers’ ancestors correspand to the requirements in this question from the DNB LOD-based dataset.
"Friends": Names of officers’ friends correspand to the requirements in this question from the DNB LOD-based dataset.
2. There are 4 formats for downloading: JSON, XML, TTL, CSV. CSV files can be opened with Microsoft® Office Excel.
3. The formal names of some titles are identical to the others’ alias, so they are both shown in the result.

*DNB LOD-based dataset: Database of Names and Biographies LOD-based dataset

1. For records in the Wooden Slips Database, set S as the wooden slip URIs with a data field value (O) of "two rows," and set the "format type" (形制類型) data field (P) as crm:P2_has_type/rdfs:label.

2. Set S as the wooden slip URIs from step 1, then query the data field (P) of schema:identifier and set O as the ID numbers.

3. Set S as the wooden slip URIs from step 1, then query the data field (P) of crm:P24i_changed_ownership_through/crm:P134i_was_continued_by/crm:P7_took_place_at/rdfs:label and set O as the excavation sites.

4. Set S as the wooden slip URIs from step 1, then query the data field (P) of crm:P108i_was_produced_by/crm:P4_has_time-Span/crm:P10_falls_within/rdfs:label and set O as the dynasty of origin.

5. Set S as the wooden slip URIs from step 1, then query the data field (P) of crm:P43_has_dimension/crm:P90_has_value and set O as the measurements of length, width, thickness, etc.

6. Order results by wooden slip URI (Item), wooden slip number (ID), format (FormatType), excavation site (Place), dynasty of origin (Period), Length, Width, Thickness, and Weight.

1. For records in the Wooden Slips Database, set S as the wooden slip URIs with a data field (O) of "perforation" (穿孔) and set the "decoration" (紋飾特徵) data field (P) as crm:P111i_was_added_by / rdfs:label.

2. Set S as the wooden slip URIs from step 1, then query the data field (P) of P2_has_type/rdfs:label and set O as the formats.

3. Set S as the wooden slip URIs from step 1, then query the data field (P) of schema:identifier and set O as the ID numbers.

4. Set S as the wooden slip URIs from step 1, then query the data field (P) of crm:P24i_changed_ownership_through/crm:P134i_was_continued_by/crm:P7_took_place_at/rdfs:label and set O as the excavation sites.

5. Order results by wooden slip URI (Item), wooden slip number (ID), Decoration, format (FormatType), and excavation site (Place).

1. For records in the Wooden Slips Database, set S as the wooden slip URIs with a data field value (O) of "zhuan" (傳) and set the "inscription word" (釋文單字) data field (P) as crm:P128_carries / crm:P3_has_note / crm:P67_refers_to / rdfs:label.

2. Set S as the wooden slip URIs from step 1, then query the data field (P) of crm:P128_carries / crm:P3_has_note / crm:P67_refers_to / dcterms:type/ rdfs:label and set O as the script style.

3. Set S as the wooden slip URIs from step 2, then query the data field (P) of crm:P24i_changed_ownership_through / crm:P134i_was_continued_by / crm:P7_took_place_at / rdfs:label and set O as the excavation site.

4. Set S as the wooden slip URIs from step 3, then query the data field (P) of crm:P108i_was_produced_by / crm:P4_has_time-Span / rdfs:label and set O as the time of creation.

5. Order results by wooden slip URI (Item), Word, Script, Place, and Time.

1. For records in the Wooden Slips Database, set S as the wooden slip URIs with a data field (O) of "burn marks" (燒痕) and set the "decoration" (紋飾特徵) data field (P) as crm:P111i_was_added_by / rdfs:label.

2. Set S as the wooden slip URIs from step 1, then query the data field (P) of crm:P24i_changed_ownership_through / crm:P134i_was_continued_by / crm:P7_took_place_at / rdfs:label and set O as the excavation sites.

3. Set S as the wooden slip URIs from step 1, then query the data field (P) of schema:identifier and set O as the ID numbers.

4. Order results by wooden slip URI (Item), wooden slip number (ID), Decoration, and excavation site (Place).

1. For records in the Wooden Slips Database, set S as the wooden slip URIs with a data field (O) of "human face format" (人面形) and "image format" (圖形), and set the "decoration" (紋飾特徵) data field (P) as crm:P111i_was_added_by / rdfs:label.

2. Set S as the wooden slip URIs from step 1, then query the data field (P) of crm:P2_has_type / rdfs:label ?FormatType and set O as the formats.

3. Set S as the wooden slip URIs from step 1, then query the data field (P) of schema:identifier and set O as the ID numbers.

4. Order results by wooden slip URI (Item), wooden slip number (ID), Decoration, and format (FormatType).

1. For records in the Wooden Slips Database, set S as the wooden slip URIs with a data field value (O) of "practice characters" (習字) and set the "Style" (書寫特徵) data field (P) as crm:P128_carries / crm:P3_has_note / crm:P67_refers_to / dcterms:description.

2. Set S as the wooden slip URIs from step 1, then query the data field (P) of crm:P128_carries / crm:P3_has_note / crm:P67_refers_to / rdfs:label and set O as the words on the slip.

3. Set S as the wooden slip URIs from step 2, then query the data field (P) of crm:P2_has_type / rdfs:label and set O as the formats.

4. Set S as the wooden slip URIs from step 3, then query the data field (P) of schema:identifier and set O as the ID numbers.

5. Order results by wooden slip URI (Item), ID, Script, Style, and format (FormatType).

1. For records in the Wooden Slips Database, set S as the wooden slip URIs with a data field (O) of "human face talisman" (人面符) and set the "format" (形制) data field (P) as crm:P2_has_type / rdfs:label.

2. Set S as the wooden slip URIs from step 1, then query the data field (P) of crm:P65_shows_visual_item / crm:P2_has_type / rdfs:label and set O as the wooden slip URIs with “color photographs” (彩色照片).

3. Set S as the wooden slip URIs from step 2, then query the data field (P) of schema:identifier and set O as the ID numbers.

4. Set S as the wooden slip URIs from step 3, then query the data field (P) of owl:sameAs and set O as the Wooden Slip Character Dictionary URLs.

5. Order results by wooden slip URI (Item), wooden slip number (ID), format (FormatType), and Wooden Slip Character Dictionary URLs (WCD_URL).

1. For records in the Wooden Slips Database, set S as the wooden slip URIs with a data field value (O) of "clerical script" (隸書) and set the "calligraphic style" (文字書體) data field (P) as crm:P128_carries / crm:P3_has_note / crm:P67_refers_to / dcterms:type / rdfs:label.

2. Set S as the wooden slip URIs from step 1, then query the data field (P) of crm:P2_has_type / rdfs:label and set O as the formats.

3. Set S as the wooden slip URIs from step 2, then query the data field (P) of schema:identifier and set O as the ID numbers.

4. Order results by wooden slip URI (Item), ID, Script, and format (FormatType).

1. For records in the Wooden Slips Database, set S as the wooden slip URIs with a data field value (O) of "yue" (月), "shi" (石), "dou" (斗), or "sheng" (升) and set the "inscription word" (釋文單字) data field (P) as crm:P128_carries / crm:P3_has_note / crm:P67_refers_to / rdfs:label.

2. Set S as the wooden slip URIs from step 1, then query the data field (P) of crm:P128_carries / crm:P3_has_note / crm:P67_refers_to / schema:url and set O as the Wooden Slips Character Dictionary URLs.

3. Set S as the wooden slip URIs from step 2, then query the data field (P) of schema:identifier and set O as the ID numbers.

4. Set S as the wooden slips URIs from step 3, then query the data field (P) of crm:P24i_changed_ownership_through / crm:P134i_was_continued_by / crm:P7_took_place_at / rdfs:label and set O as "A8 City Ruins" (A8 破城子) excavation sites.

5. Set as the wooden slips URIs from step 4, then query the data field (P) of schema:identifier and set O as the ID numbers.

6. Order results by wooden slip URI (Item), ID, Word, Place, and Wooden Slips Character Dictionary URL (WCD-URL).

1. For records in the Wooden Slips Database, set S as the wooden slip URIs with a data field value (O) of "lingshichong" (令史充) or "/lingshichong" (╱令史充) and set the "recognized word content" (釋文內容) data field (P) as crm:P128_carries / dcterms:description.

2. Set S as the wooden slip URIs from step 1, then query the data field (P) of crm:P24i_changed_ownership_through / crm:P134i_was_continued_by / crm:P7_took_place_at / rdfs:label and set O as the excavation sites.

3. Set S as the wooden slip URIs from step 2, then query the data field (P) of schema:identifier and set O as the ID numbers.

4. Set S as the wooden slips URIs from step 3, then query the data field (P) of crm:P108i_was_produced_by / crm:P4_has_time-Span / rdfs:label and set O as the time of creation.

5. Order results by wooden slip URI (Item), ID, Inscription, Place, and Time.

1. For records in the Wooden Slips Database, set S as the wooden slip URIs with a data field value (O) of "zhuan" (專) and set the "character component" (單字部件) data field (P) as crm:P128_carries / crm:P3_has_note / crm:P67_refers_to / ascdc:characterComponent.

2. Set S as the wooden slip URIs from step 1, then query the data field (P) of crm:P128_carries / crm:P3_has_note / crm:P67_refers_to / dcterms:type / rdfs:label and set O as the words written in "clerical script" (隸書).

3. Order results by wooden slip URI (Item), Word, Component, and Script.

1. For records in the Wooden Slips Database, set S as the wooden slip URIs with a data field (O) of notched" (刻齒) and set the "decoration" (紋飾特徵) data field (P) as crm:P111i_was_added_by / rdfs:label.

2. Set S as the wooden slip URIs from step 1, then query the data field (P) of crm:P24i_changed_ownership_through / crm:P134i_was_continued_by / crm:P7_took_place_at / rdfs:label and set O as the excavation sites.

3. Set S as the wooden slip URIs from step 2, then query the data field (P) of crm:P2_has_type / rdfs:label and set O as the formats.

4. Set S as the wooden slip URIs from step 3, then query the data field (P) of schema:identifier and set O as the ID numbers.

5. Order results by wooden slip URI (Item), wooden slip number (ID), Decoration, and format (FormatType).

1) For records in the Qing Secret Societies Database, set S as data value "Qingcha sect" (清茶門教), then query the data field (P) of gndo:relatedTerm / rdfs:label and set O as deity of the sect.
2) Set S as URI of the "Qingcha sect" from step 1, then query the data field (P) of gndo:subjectHeading / rdfs:label and set O as data value of the Sutra.
3) Set S as URI of the "Qingcha sect" from step 1, then query the data field (P) of skos:related / rdfs:label and set O as data value of Tools for religious practices.
4) Set S as URI of the "Qingcha sect" from step 1, then query the data field (P) of crm:P3_has_note / rdfs:label and set O as data value of sectarian Definition.
5) Set S as URIs of the sectrarian "Definiton" from step 4, then query the data field (P) of crm:P2_has_type and set O as data value of Tyeps of sectarian Definition.
6) Order the results by Group URI, GroupName, Deity, Sutra, Tool, DefinitionText and DefinitionType.

1) For records in the Qing Secret Societies Database, set S as data value "Sect Event of Wang Dianqui" (王殿魁案), then query the data field (P) of crm:P7_took_place_at / rdfs:label and set O as Place name.
2) Order the results by Event URI, Event_Name and Place.

1) For records in the Qing Secret Societies Database, set S as URIs of "Person", then query the data field (P) of crm:P107i_is_current_or_former_member_of / rdfs:label and set O as sect Group.
2) Set S as URIs of the "Person" from step 1, then query the data field (P) of crm:P11i_participated_in and set O as sect event.
3) Set S as URIs of the "sect event" from step 2, then query the data field (P) of crm:P9_consist_of / rdfs:label and set O as data value of Crime Type.
4) Deduct the data of Person URI of "Chen Chaoyu" (陳潮玉) and define the data value of sect group as "Sifokou Sect" (石佛口王姓邪教).
5) Order the results by Person URI, Name, Group and CrimeType.

1) For records in the Qing Secret Societies Database, set S as URIs of "Person", then query the data field (P) of crm:P107i_is_current_or_former_member_of / rdfs:label and set O as sect Group.
2) Set S as URIs of the "Person" from step 1, then query the data field (P) of bio:father / rdfs:label and set O as names of Father.
3) Conduct the same query as last step and include the names of Father shown as string value.
4) Order the results of union search by Person URI, Name, Group and Father.

1) For records in the Qing Secret Societies Database, set S as URIs of "Person", then query the data field (P) of agrelon:hasStudent and set O as names of Student.
2) Set S as URIs of the "Person" from step 1, then query the data field (P) of bio:father / rdfs:label and set O as names of Father.
3) Repeat the same query as step1, and set S as URIs of the "Person", then query the data field (P) of pext:hasSon / rdfs:label and set O as names of Son.
4) Filter the results of union search, in which names of student are appeared more than once.
5) Order the results by Person URI, Name, Student, Father and Son.

1) For records in the Qing Secret Societies Database, set S as URIs of "Person", then query the data field (P) of crm:P107i_is_current_or_former_member_of / rdfs:label and set O as sect Group.
2) Set S as URIs of the "Group" from step 1, then query the data field (P) of skos:broadMatch / rdfs:label and set O as Group Type.
3) Set S as URIs of the "Person" from step 1, then query the data field (P) of schema:hasOccupation / rdfs:label and set O as Occupation.
4) Set S as URIs of the "Occupation" from step 3, then query the data field (P) of skos:broadMatch / rdfs:label and set O as Occupation Type.
5) Order the results of union search by Person URI, Name, Group, GroupType, Occupation and OccupationType.

1) For records in the Qing Secret Societies Database, set S as URIs of "Person", then query the data field (P) of rdfs:label and set O as data value of Person's name.
2) Set S as URIs of the "Person" from step 1, then query the data field (P) of crm:P107i_is_current_or_former_member_of / rdfs:label and set O as sect Group.
3) Set S as URIs of the "Person" from step 1, then query the data field (P) of schema:familyName and set O as Family Name.
4) Filter the data value of "Sect Group" as "Qingcha sect" (清茶門教) and count the appearance of each "Family Name".
5) Order the results by FamilyName and Count of each appeared family name.

1) For records in the Qing Secret Societies Database, set S as URIs of "Person", then query the data field (P) of rdfs:label and set O as data value of Person's name.
2) Set S as URIs of the "Person" from step 1, then query the data field (P) of crm:P107i_is_current_or_former_member_of / rdfs:label and set O as sect Group.
3) Set S as URIs of the "Person" from step 1, then query the data field (P) of ascdc:nativePlace and set O as Place Name.
4) Set S as URIs of the "Person" from step 1, then query the data field (P) of schema:familyName and set O as Family Name.
5) Filter the data value of "Sect Group" as "Qingcha sect" (清茶門教) and "Shifokou Sect" (石佛口王姓邪教) , and also limit the data value of "Family Name" as "Wang" (王).
6) Order the results by Person URI, Name, Group, Place and FamilyName.

1) For records in the Qing Secret Societies Database, set S as URIs of "Person", then query the data field (P) of rdfs:label and set O as data value of Person's name.
2) Set S as URIs of the "Person" from step 1, then query the data field (P) of crm:P11i_participated_in and set O as sect Activity.
3) Set S as URIs of the "Sect Acitvity" from step 2, then query the data field (P) of ascdc:ageAtTime and set O as Age.
4) Filter the URIs of "Sect Activity" containing the segment of "Mission".
5) Order the results by Person URI, Name and Age.

1) For records in the Qing Secret Societies Database, set S as URIs of "Person", then query the data field (P) of rdfs:label and set O as data value of Person's name.
2) Set S as URIs of the "Person" from step 1, then query the data field (P) of gvp:ulan1108_influenced_by and set O as Mentor's name.
3) Filter the data values acquired from the step 2, which contain the Chinese word "shi" (氏).
4) Order the results by Person URI, Name and Mentor.

1) For records in the Qing Secret Societies Database, set S as URIs of "Sect Event", then query the data field (P) of rdfs:label and set O as data value of Event's name.
2) Set S as URIs of the "Sect Event" from step 1, then query the data field (P) of crm:P9i_forms_of / rdfs:label and set O as Sect.
3) Filter the URIs of "Sect Event" containing the segment of "Activity".
4) Set S as URIs of the "Sect Event" from step 2, then query the data field (P) of crm:P15i_influenced / rdfs:label and set O as types of Punishment.
5) Order the results by Event URI, Event Name, Sect, Punishment and Age.

1) For records in the Qing Secret Societies Database, set S as URIs of "Sect Event", then query the data field (P) of rdfs:label and set O as data value of Event's name.
2) Set S as URIs of the "Sect Event" from step 1, then query the data field (P) of crm:P17_was_motivated_by / rdfs:label and set O as Background Event.
3. Order the results by Event URI, EventName and BackgroundEvent.

1) For records in the Qing Secret Societies Database, set S as URIs of "Archive", then query the data field (P) of rdfs:label and set O as data value of Archive's name.
2) Set S as URIs of the "Archive" from step 1, then query the data field (P) of gndo:relatedCorperateBody and set O as related Official Organization.
3) Set S as URIs of the "Archive" from step 1, then query the data field (P) of crm:P128_carries / crm:P67_refers_to and set O as related Sect Event.
4) Filter the URIs of "Sect Event" containing the segment of "Event".
5) Set S as URIs of the "Sect Event" from step 3, then query the data field (P) of rdfs:label and set O as data values of name of the related Sect Event.
6) Order the results by Archive URI, Label, OfficialOrganization and Event.

1) For records in the Qing Secret Societies Database, set S as URIs of "Person", then query the data field (P) of rdfs:label and set O as data value of Person's name.
2) Set S as URIs of "Person" from step 1, then query the data field (P) of crm:P2_has_type / rdfs:label and set O as data value of Person's type with filtration of data value as "Officier" (官員).
3) Set S as URIs of the "Person" from step 1, then query the data field (P) of crm:P11i_participated_in and set O as Event Activity.
4) Set S as URIs of the "Event Activity" from step 3, then query the data field (P) of leo:involved / rdfs:label and set O as names of official Position.
5) Set S as URIs of the "Event Activity" from step 3, then query the data field (P) of crm:P9i_forms_part_of / rdfs:label and set O as Sect Event with filtration of data value as "Sect Event of Wang Dianqui" (王殿魁案).
6) Order the results by Person URI, Name, PersonType, Position and Event.

1) For records in the Qing Secret Societies Database, set S as URIs of "Person", then query the data field (P) of rdfs:label and set O as data value of Person's name.
2) Set S as URIs of "Person" from step 1, then query the data field (P) of crm:P2_has_type / rdfs:label and set O as Person's type with filtration of data value as "Officier" (官員).
3) Set S as URIs of the "Person" from step 1, then query the data field (P) of crm:P11i_participated_in and set O as Event Activity.
4) Set S as URIs of the "Event Activity" from step 3, then query the data field (P) of crm:P9i_forms_part_of / rdfs:label and set O as Sect Event.
5) Set S as URIs of the "Event Activity" from step 3, then query the data field (P) of leo:involved / rdfs:label and set O as Official Position.
6) Set S as URIs of the "Official Positon" from step 5, then query the data field (P) of rdfs:label and set O as names of Official Position.
7) Set S as URIs of the "Official Positon" from step 5, then query the data field (P) of owl:sameAs and set O as URIs of Official Position in the Dataset of Qing Official Titles (DQOT).
8) Set S as URIs of the "Position in DQOT" from step 7, then query the data field (P) of ascdc:positionRank and set O as Position Rank.
9) Order the results by Person URI, Name, PersonType, Position, DQOT and Rank.

1) For records in the Qing Secret Societies Database, set S as URIs of "Event", then query the data field (P) of rdfs:label and set O as Event's name with filtration of URIs containing the segment of "Event"
2) Set S as URIs of "Event" from step 1, then query the data field (P) of time:P2_hasTime and set O as Event's time with filtration of data value as "Jiaqing" (嘉慶).
3) Order the results by Event URI, Event Name and Time.

1) For records in the Qing Secret Societies Database, set S as URIs of "Person", then query the data field (P) of rdfs:label and set O as data value of Person's name.
2) Set S as URIs of "Person" from step 1, then query the data field (P) of crm:P2_has_type / rdfs:label and set O as Person's type with filtration of data value as "Sect Participant" (宗教參與者).
3) Set S as URIs of the "Person" from step 1, then query the data field (P) of crm:P11i_participated_in and set O as sect Activity Event.
4) Set S as URIs of the "Event Activity" from step 3, then query the data field (P) of crm:P9i_forms_part_of / rdfs:label and set O as Sect Event.
5) Set S as URIs of the "Event Activity" from step 3, then query the data field (P) of crm:P15i_influenced / rdfs:label and set O as Results of sentencing with filtration of data value as "linchgi" (凌遲).
6) Set S as URIs of the "Event Activity" from step 3, then query the data field (P) of crm:P9_consist_of / rdfs:label and set O as Crime Type.
7) Order the results by Person URI, Name, Event, Result and CrimeType.

1) For records in the Qing Secret Societies Database, set S as URIs of "Group", then query the data field (P) of gndo:relatedTerm / rdfs:label and set O as group's Deity with filtration of data value as "Maitreya Buddha" (彌勒佛).
2) Set S as URIs of "Group" from step 1, then query the data field (P) of gndo:relatedSubjectHeading / rdfs:label and set O as Sutra.
3) Order the results by Deity URI, Deity, Sutra URI and Sutra.

1) Search the place name containing value with ""Chishang Township"" (池上鄉) by using property as ""gn:parentADM3.""\n2) Search reference titles containing value with ""Chishang"" (池上) by using property as ""schema:name.""\n3) Search titles of government materials containing value with ""Chishang"" (池上) by using property as ""schema:name.""\n4) Search events and multimedia that happen or are collected in Chishang.\n5) Search titles of field investigation reports containing value with ""Chishang"" (池上) by using property as ""schema:name.""\n6) Combine the data obtained from the above steps and display the results after data URI, titles and types of dataset.

1) Search the field location where the local natural crops (dbo:produces) are ""rice"".\n2) Seach the demographic information, such as population (gn:population), male population (ascdc:populationMen), female population (ascdc:populationFemale),elderly population (ascdc:populationOver65), of the field location, which is retrieved by the aforesaid step.

1) Search all the events (valued as ""ReportEventType=001"") related to the ""god-inviting ceremony"" during the Zhongyuan festival in Chishang Township.\n2) Search the time of event (schema:startDate), place of event (schema:location), longitude (schema:latitude) and latitude (schema:longitude) of the place (schema:longitude), and the statues of god or their representatives (dcterms:relation) obtained after each ceremony.

1) Search and list all the types of class instances (rdf:type) contained in the dataset.\n2) Count the number of instances by different class types (rdf:type).

1) Search and list all the properties applied in the dataset.\n2) Count the numbers by different property types.

1) Search and list the title (dcterms:title), description (dcterms:description), publisher (dcterms:publisher) and released date (dcterms:issued) of the SCSRT-dataset, which is structured after the DCAT model. \n2) Search and list the license condition (dcterms:license), URL allocation (dcat:accessURL), capacity (dcat:byteSize) and compressed format (dcat:compressedFormat) of the SCSRT-dataset, which is structured in the class of ""Distribution"" as designed in the DCAT model.