Spatialising Sarah Barclay Johnson's travelogue around Jerusalem (1858)
Abstract
Introduction
Delving into the pages of "Hadji in Syria: or, Three years in Jerusalem" by Sarah Barclay Johnson 1858, this project sets out to digitally map the toponyms embedded in Johnson's 19th-century exploration of Jerusalem with the wish to connect the past and the present. By visualizing Johnson's recorded toponyms, this project aims to offer a dynamic tool for scholars and enthusiasts, contributing to the ongoing dialogue on the city's historical evolution.
This spatialization, in its attempt, pays homage to Johnson's literary contribution, serving as a digital window into the cultural crossroads: Jerusalem. The project invites users to engage with the city's history, fostering a deeper understanding of its rich heritage and the interconnected narratives that have shaped the city. In this fusion of literature, history, and technology, we hope to embark on a digital odyssey, weaving a narrative tapestry that transcends time and enriches our collective understanding of Jerusalem's intricate past.
Motivation
Deliverables
- Pre-processed textual dataset of the book.
- Application results of NER using Spacy and GPT-4 on the book's text.
- Comparative analysis report of NER effectiveness between Spacy and GPT-4.
- Manually labelled dataset for a selected chapter for NER validation.
- QGIS mapping files visualizing named locations from selected chapters and the entire book.
- Visual representative maps of the narrative journey, highlighting key locations and paths.
- Developed scripts for automating Wikipedia page searches and extracting location coordinates.
- Dataset with matched coordinates for all identified locations.
- A developed platform to display project outputs.
Methodology
Assessing and Preparing OCR-Derived Text for Analysis
In our project, which involved analyzing a specific book, the initial step was to acquire the text version of the book. We found and downloaded the OCR text from Google Books and then assessed the quality of the textual data. A key metric in our assessment was the ratio of “words in the text that exist in a dictionary” to “total words” in the text, calculated using the NLTK library. Considering the book's inclusion of multiple languages, we set a threshold of 70% for this ratio. If met or exceeded, we regarded the text's quality satisfactory for our analysis purposes.
Following this quality assessment, we proceeded with text preprocessing, adapted to the specific needs of our study. Notably, we chose not to remove stop words or convert the text to lowercase, maintaining the original structure and form of the text.
Detecting Locations
NER with Spacy
- Maybe we can add some examples
- Nil & Jiaming
//LIST or visual
| Toponym Name | NER Label | something |
|---|---|---|
| Sa | aa | aa |
So, we can see the problem is mislabeling: in theory we only need to retrieve the toponyms, i.e. “GPE” & “LOC”, but SpaCy labelled some of them as “PERSON” or “ORG”. In other words, if we only select “GPE” and “LOC”, we’ll lose some toponyms; if we also select “ORG” and “PERSON”, we’ll get some non-toponyms.
Difficulties when working with historical content
When applying Named Entity Recognition (NER) with Spacy to historical content, we encountered significant challenges. The main problem was the frequent misnaming of locations, which is a result of place names changing over time, especially in historical and biblical contexts. These names often have varied across multiple languages, adding to the complexity. Furthermore, even by reading, it was occasionally challenging to determine the current significance or identity of these names due to their changing nature over centuries. This complexity highlighted how essential it is to understand the relationships between locations and what they mean within the book's narrative along with to representing a linguistic and technical challenge. It is critical to comprehend these relationships because they have a significant impact on how the text is interpreted and understood overall.
GPT-4
Preliminary Analysis for Model Selection - Assessment Focusing on Chapter 3
Manual detection
In our preliminary analysis for model selection, we focused on Chapter 3 for a detailed assessment. The initial step involved manually detecting and labeling named entities, specifically locations mentioned in the text. This was achieved by highlighting relevant text segments and subsequently gathering these identified locations into a spreadsheet. To ensure the accuracy of our location identification, each location was cross-referenced with its corresponding Wikipedia page. This was an important step, especially in cases where the context of the book made it challenging to understand the exact nature of the places mentioned, even after analyzing the entire paragraph. This method provided a solid foundation for our named entity recognition approach.
Spacy Results
- Jiaming
GPT-4 Results
- Daniele
Since the GPT-4 Results outperformed the results of Spacy NER, presented GPT-4 prompt has been used to retrieve the locations in the book.
Matching Wikipedia Pages
Using the Wikipedia API , locations identified by GPT were searched in Wikipedia, and the first relevant result was recorded. Additionally, the first image found on the page of the recorded link was retrieved. This approach was primarily used to verify the accuracy of manually determined locations. Subsequently, after all locations were obtained, it was used both for visualizing the author's path and for acquiring coordinates for locations without coordinates.
| Chapter | Count of Geometry | Count of Location |
|---|---|---|
| 1 | 1 | 7 |
| 2 | 2 | 16 |
| 3 | 21 | 32 |
| 4 | 9 | 16 |
| 5 | 4 | 6 |
| 6 | 1 | 4 |
| 7 | 4 | 11 |
| 8 | 7 | 10 |
| 9 | 2 | 7 |
| 10 | 4 | 8 |
| 11 | 3 | 8 |
| 12 | 2 | 4 |
| 13 | 4 | 6 |
| 14 | - | 4 |
| 16 | 4 | 12 |
| 18 | 4 | 7 |
| 19 | 2 | 7 |
| 20 | 3 | 5 |
| Grand Total | 77 | 170 |
Tracking Author's Route on Maps
Finalizing the List of Coordinates
1. Fuzzy matching GPT-4 results with an existing location list
We've got a list of existing toponyms in Jerusalem that were extracted previously from one map with coordinates. The list is multi-lingual, which means there might be multiple names for one place in different languages including English, Arabic, German, and Hebrew. Considering toponyms that we retrieved from the travelogue could be in languages other than English (perhaps quotes or references to historical/cultural stuff) and there might be slightly different ways to refer to the same place, a fuzzy matching algorithm is applied to match the toponyms GPT retrieved and the toponyms in multiple languages from the list. We used "fuzzywuzzy" package and set the similarity_score over 80 as the passing standard. After fuzzy matching, we got X unique toponyms with Y unique coordinates.
2. Retrieving coordinates by matched Wikipedia pages
Utilizing previously obtained Wikipedia links, coordinates were gathered using a web scraping method. To ensure the exclusion of broader locations such as the 'Mediterranean Sea,' the coordinates obtained were filtered to focus specifically on the Jerusalem region. For locations where coordinates could not be determined in the previous step, additional coordinate information was added, culminating in the final version of the dataset being recorded.
Visualization by GeoPandas
Daniele
- QGIS
- GeoPandas
Creating a Platform for Final Output
Jiaming
Results
Limitations and Further Work
- API for a smoother process - Improve with the full book instead of chapter by chapter
automated application for all historical context
augmented interaction on map
Conclusion
Project Timeline & Milestones
| Timeframe | Task | Completion |
|---|---|---|
| Week 4 |
|
✓ |
| Week 5 |
|
✓ |
| Week 6 |
|
✓ |
| Week 7 |
|
✓ |
| Week 8 |
|
✓ |
| Week 9 |
|
✓ |
| Week 10 |
|
✓ |
| Week 11 |
|
✓ |
| Week 12 |
|
✓ |
| Week 13 |
|
✓ |
| Week 14 |
|
GitHub Repository
Course: Foundation of Digital Humanities (DH-405), EPFL
Professor: Frédéric Kaplan
Supervisors:
Authors: