<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>P. Smith);</journal-title>
      </journal-title-group>
      <issn pub-type="ppub">1613-0073</issn>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Assessing Performance in Extracting Topological, Direction and Distance Spatial Relations from Reddit using LLMs</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Paddy Smith</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ed Manley</string-name>
          <email>e.j.manley@leeds.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Myles Gould</string-name>
          <email>m.i.gould@leeds.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Workshop</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Institute for Spatial Data Science, School of Geography, University of Leeds</institution>
          ,
          <country country="UK">UK</country>
        </aff>
      </contrib-group>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0002</lpage>
      <abstract>
        <p>This paper provides an initial exploration of the capabilities of large language models (LLMs) to extract spatial relations from unstructured social media text. The approach examines the performance of GPT-4o and Gemini 1.5-Pro using a diverse set of spatial relation terms, and seeks to determine whether certain spatial relation types (topological, distance and direction) are more challenging to extract. To evaluate, GPT-4o and Gemini 1.5-Pro output is compared to manually labeled spatial relation triplets from Reddit place descriptions. The findings demonstrate challenges in extracting spatial relations for LLMs, with the highest model only achieving 0.48 precision. However, performance varied across spatial relation types, as direction relations were extracted with higher precision (0.75) compared to distance relations (0.62) and topological relations (0.35).</p>
      </abstract>
      <kwd-group>
        <kwd>Spatial relation extraction</kwd>
        <kwd>Large Language Models (LLMs)</kwd>
        <kwd>Social media</kwd>
        <kwd>Reddit</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Generally, they are categorized as either topological, direction or distance, and represented in
natural language with terms like ‘in’, ‘above’ or ‘near6’][. Methods for extracting spatial relations from
natural language have developed in computer science and GIScience7][, and common methods include;
dictionary-based, supervised machine learning and deep neural network8s][.
      </p>
      <p>
        Extracting spatial relations from unstructured text, like Reddit, remains a challenge for established
methods, for several reasons. Spatial relation triplets may not follow a simple syntactic structure
of &lt;subject, relation, object&gt; (e.g.“check out the nice parts of Bradford, such as Ilkley and Saltaire.”),
terms used can be complex and contextual (e.g.‘about 10 minute drive’), and applied presuming spatial
knowledge (e.g. “Camden is just past King’s Cross.”) [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. LLMs may be able to tackle these challenges.
For instance, identifying informal spatial relation terms (abbreviations, slang and creative spelling)
via their vast training corpus, recognize ambiguously used spatial relations due to greater contextual
semantic understanding or infer implicit references using spatial reasoning.
Italy
      </p>
      <p>CEUR</p>
      <p>ceur-ws.org</p>
      <p>This study is an initial exploration into the capabilities of using LLMs to extract explicit spatial
relation triplets from a manually annotated Reddit text corpus. Preliminary experiments test LLM’s
ability to identify spatial relation terms across general types and sub-types. By focusing on explicit
spatial relations, LLMs semantic interpretation of text is explored, not its ability to infer implicit relations
through reasoning.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <p>
        LLMs have already shown impressive capabilities in information extraction tasks, including NER10[]
and relation extraction 1[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], and also toponym recognition and resolution1[
        <xref ref-type="bibr" rid="ref2">2, 13</xref>
        ]. Initial attempts
have been made towards assessing LLMs capabilities in spatial relation tasks. A subset of this work
has explored LLMs spatial reasoning ability to infer spatial relations14[, 15]. A few papers have also
evaluated LLMs ability to extract explicit spatial relations from text. Ramrakhiyani et a[l1. 6] combines
natural language inference (NLI) with LLMs to extract border orientations between countries within
Wikipedia text data, achieving high precision results. Hu et al[.17] uses GPT-4 to extract a range of
spatial relations from Wikipedia text, however performance is not evaluated. Haris et[a1l8.] tests three
separate LLMs (GPT, Llama and Gemini) to extract a selection of spatial relation terms from the Corpus
of the Lake District Writings (CLDW). The results showed high performance for GPT-4, however the
models produced inaccuracies, including extracting spatial relations that did not exist in the text.
      </p>
      <p>There are several directions this preliminary work can be extended. So far, there have been limited
attempts to extract spatial relations from unstructured tex1t8[], and from social media data. Furthermore,
no study has compared LLM’s performance in extracting spatial relation terms across spatial relation
types (topological, distance and direction). Finally, the use of prompts has been relatively unexplored,
as previous work has only used zero-shot prompting.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Approach</title>
      <sec id="sec-3-1">
        <title>3.1. Test set</title>
        <p>Reddit data collected by Berragan et al[.19] was used in this study. The dataset consists of Reddit posts
and comments from 186 UK place-based subreddits, posted between 2011 to 2022. To evaluate LLMs
performance, text from the subreddit r/Leeds were manually annotated to create the test set. Triplets
were labelled if they contain a subject (a reference to a place to be located), a spatial relation term and
an object (a reference to a place already located), in the form &lt;subject, relation, object&gt;. A place was
defined as any named location (e.g., ‘Leeds’, ‘Headingley’), or generic place descriptor (e.g., ‘home’, ‘city
center’).</p>
        <p>Each triplet within the test set was assigned to spatial relation general-type (topological, distance or
direction) and six sub-types (see Figure1), which have been defined in [ 20]. Only containment and
connectivity relations were chosen for topological spatial relations, as terms relating to other topological
relations were not frequently present in the Reddit text corpus. Natural language terms were assigned
to a general type and sub-type, aided by previous work21[, 22].</p>
        <p>In total, 300 spatial relation triplets were labeled from the Reddit text corpus. A comment or post
may contain multiple spatial relation triplets. It was ensured that equal amounts of triplets for each
spatial relation general type and sub-type were present within the test set. An additional 600 comments
or posts that did not contain spatial relation triplets (non-spatial) were included in the test set to better
reflect the sparsity of such relations in the Reddit text corpus. This also enabled the evaluation of false
positives, allowing assessment of whether LLMs incorrectly extracted spatial relationships that were
not present in the text.</p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Prompt-engineering</title>
        <p>
          Prompts were designed to include definitions for spatial relation sub-types, and to constrain the LLM to
only extract explicit spatial relations (see AppendixA). Additionally, place names were not provided
as an input, therefore the model is required to extract them. The base prompt is used for the
zeroshot approach, which does not provide any training data. It is then adapted for two diferent prompt
approaches (AppendixB). Few-shot prompting uses examples, and chain-of-thought provides reasoning
steps to improve model performance2[
          <xref ref-type="bibr" rid="ref3">3, 24</xref>
          ].
        </p>
        <p>To extract the spatial relation triplets, GPT-4o and Gemini 1.5-Pro was used via OpenA2I5[] and
Google AI [26] API services. The outputs were compared to the test set, and performance is evaluated
using precision, recall and F1-score. A correct spatial relation triplet includes exact place names and
spatial relation term found in the text, in the correct order and with the correct general type and
sub-type labels. Performance scores for each spatial relation general-type and sub-type were calculated
as an average across the three prompt approaches.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Experiments and Evaluation</title>
      <p>The results of the experiment are presented in Tabl1e. Overall, GPT-4o and Gemini 1.5-Pro exhibited
moderate performance scores, with lower than expected precision. Few-shot and chain-of-thought</p>
      <sec id="sec-4-1">
        <title>Zero-shot</title>
      </sec>
      <sec id="sec-4-2">
        <title>Few-shot</title>
      </sec>
      <sec id="sec-4-3">
        <title>Chain of Thought</title>
      </sec>
      <sec id="sec-4-4">
        <title>Topological</title>
        <p>Containment
Connectivity</p>
      </sec>
      <sec id="sec-4-5">
        <title>Direction</title>
        <p>Relative Direction
Cardinal Direction</p>
      </sec>
      <sec id="sec-4-6">
        <title>Distance</title>
        <p>Quantitative Distance
Qualitative Distance
prompting appeared to improve performance across the models with higher recall scores. Precision
and recall scores varied by spatial relation type considerably, as certain spatial relations were more
challenging to extract (Figure2).</p>
        <p>Direction relations were less challenging compared to topological and distance relations. In particular,
cardinal relations were extracted with high precision (exampale). Likewise, topological connectivity
relations were easily identified and captured by the models (exampleb).</p>
        <p>Most spatial relation sub-types had lower recall compared to precision, therefore the models was
confident in predictions but missed relevant cases. In particular, quantitative distance relations proved
challenging, as both models frequently missed numerical spatial relation terms (exampcle). In contrast,
relative direction and qualitative distance had lower precision scores, as the terms often rely on spatial
references and interpretation, making them more prone to inaccuracies (examdp)l.e</p>
        <p>Finally, containment relation proved the most challenging for GPT-4o and Gemini 1.5-Pro. Contrasting
to other spatial relations, it produced very low precision scores. Examining the output, there was a high
frequency of implied ‘in’ relations. Some of these were geographically correct however did not explicitly
appear in the text, whilst others were presumed due to the sentence structure (examep)l.eSimilar
ifndings have been reported in previous studies [18], and have been attributed to LLM’s tendency to
hallucinate information that appears plausible but is not grounded in the input text.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusion</title>
      <p>This paper presents initial experiments using LLMs to extract explicit spatial relations from Reddit.
Both GPT-4o and Gemini 1.5-Pro encountered significant challenges in this task, exhibiting numerous
inaccuracies and missed cases. However, ability to extract spatial relations varied across diferent types,
warranting further investigation. One possible explanation is the presence of biases in training datasets.
For instance, topological and directional relations, such a“snext to” or“north of”, may be overrepresented,
leading to better generalization for these types of relations. Additionally, understanding the extent to
which LLMs rely on memorization versus reasoning remains an open questio2n7][. This is particularly
relevant for Reddit-based data, given its reported inclusion in LLM training corpor2a8][.</p>
      <p>Future research should explore techniques to enhance LLM performance, including the integration of
geographic knowledge [17]. For topological relations, resources such as gazetteers and spatial ontologies
could validate containment relationships. Retrieval-augmented generation (RAG) approaches may help
mitigate hallucinations by incorporating external knowledge source2s9[].</p>
      <p>Although the findings are specific to the manually annotated dataset, further investigation using
benchmark datasets is needed. Nevertheless, this experiment establishes an initial foundation for future
assessments of LLM’s capabilities in spatial relation extraction.</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgments</title>
      <p>This research has been funded by Economic and Social Research Council (ESRC) via the White Rose
Doctoral Training Partnership (WRDTP).</p>
    </sec>
    <sec id="sec-7">
      <title>Declaration on Generative AI</title>
      <p>The authors used ChatGPT to rephrase sentences to improve clarity and conciseness. Any suggestions
were reviewed and edited as needed, and the authors take full responsibility for the publication’s
content.
[13] K. Kopanov, Comparative Performance of Advanced NLP Models and LLMs in Multilingual
GeoEntity Detection, in: Proceedings of the Cognitive Models and Artificial Intelligence Conference,
ACM, İstanbul Turkiye, 2024, pp. 106–110. doi1:0.1145/3660853.3660878.
[14] A. G. Cohn, R. E. Blackwell, Evaluating the Ability of Large Language Models to Reason about</p>
      <p>Cardinal Directions, 2024. doi1:0.48550/ARXIV.2406.16528.
[15] N. Fulman, A. Memduhoğlu, A. Zipf, Distortions in Judged Spatial Relations in Large Language</p>
      <p>Models, The Professional Geographer (2024) 1–9. do1i0: .1080/00330124.2024.2372792.
[16] N. Ramrakhiyani, V. Vasudeva, K. Girish, Extracting Orientation Relations between Geo-Political</p>
      <p>Entities from their Wikipedia Text, GeoExT@ ECI (2023) 44–50.
[17] L. Hu, W. Li, J. Xu, Y. Zhu, GeoEntity-type constrained knowledge graph embedding for predicting
natural-language spatial relations, International Journal of Geographical Information Science
(2024) 1–24. doi:10.1080/13658816.2024.2412731.
[18] E. Haris, A. G. Cohn, J. G. Stell, Exploring Spatial Representations in the Historical Lake District</p>
      <p>Texts with LLM-based Relation Extraction, 2024. doi1:0.48550/ARXIV.2406.14336.
[19] C. Berragan, A. Singleton, A. Calafiore, J. Morley, Mapping cognitive place associations within
the United Kingdom through online discussion on Reddit, Transactions of the Institute of British
Geographers (2024) tran.12669. do1i:0.1111/tran.12669.
[20] P. Kordjamshidi, M. Van Otterlo, M.-F. Moens, Spatial Role Labeling Annotation Scheme, in: N. Ide,
J. Pustejovsky (Eds.), Handbook of Linguistic Annotation, Springer Netherlands, Dordrecht, 2017,
pp. 1025–1052. doi:10.1007/978-94-024-0881-2_38.
[21] J. Chen, A. G. Cohn, D. Liu, S. Wang, J. Ouyang, Q. Yu, A survey of qualitative spatial
representations, The Knowledge Engineering Review 30 (2015) 106–136. do1i:0.1017/S0269888913000350.
[22] M. Egenhofer, D. M. Mark, R. Sharif, Natural-Language Spatial Relations Between Linear and
Areal Objects: The Topology and Metric of English-Language Terms, International Journal of
Geographical Information Science 12 (1998) 215–246.
[23] S. Min, X. Lyu, A. Holtzman, M. Artetxe, M. Lewis, H. Hajishirzi, L. Zettlemoyer, Rethinking the
Role of Demonstrations: What Makes In-Context Learning Work?, 2022. do1i0:.48550/ARXIV.
2202.12837.
[24] A. Gao, Prompt Engineering for Large Language Models, SSRN Electronic Journal (2023). d1o0.i:
2139/ssrn.4504303.
[25] OpenAI, Models: Gpt-4o (128k context window), 2023. URL:https://platform.openai.com/docs/
models#gpt-4o, large language model.
[26] Google, Gemini 1.5 pro: A multimodal mixture-of-experts model with extended context window,
2024. URL: https://ai.google.dev/gemini-api/docs/models#gemini-1.5-pr,olarge language model.
[27] J. Roberts, T. Lüddecke, S. Das, K. Han, S. Albanie, GPT4GEO: How a Language Model Sees
the World’s Geography, 2023. URL:https://arxiv.org/abs/2306.00020. doi:10.48550/ARXIV.2306.
00020.
[28] H. Field, Reddit soars after announcing OpenAI deal that allows use of its
data for training AI models (2023). URL: https://www.cnbc.com/2024/05/16/
reddit-soars-after-announcing-openai-deal-on-ai-training-models.html#:~:text=Reddit%
20soars%20after%20announcing%20OpenAI%20deal%20that,previously%20announced%20a%
20similar%20deal%20with%20Google.
[29] W. Fan, Y. Ding, L. Ning, S. Wang, H. Li, D. Yin, T.-S. Chua, Q. Li, A Survey on RAG Meeting
LLMs: Towards Retrieval-Augmented Large Language Models, in: Proceedings of the 30th ACM
SIGKDD Conference on Knowledge Discovery and Data Mining, ACM, 2024, pp. 6491–6501. URL:
https://dl.acm.org/doi/10.1145/3637528.3671470. doi:10.1145/3637528.3671470.</p>
    </sec>
    <sec id="sec-8">
      <title>A. Base Prompt Used</title>
    </sec>
    <sec id="sec-9">
      <title>B. Prompt Approaches</title>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>B. I.</given-names>
            <surname>Davidson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Wischerath</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Racek</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. A.</given-names>
            <surname>Parry</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Godwin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Hinds</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. Van Der</given-names>
            <surname>Linden</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. F.</given-names>
            <surname>Roscoe</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Ayravainen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. G.</given-names>
            <surname>Cork</surname>
          </string-name>
          ,
          <article-title>Platform-controlled social media APIs threaten open science</article-title>
          ,
          <source>Nature Human Behaviour</source>
          <volume>7</volume>
          (
          <year>2023</year>
          )
          <fpage>2054</fpage>
          -
          <lpage>2057</lpage>
          .
          <year>do1i</year>
          :
          <fpage>0</fpage>
          .1038/s41562-023-01750-2.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>H.</given-names>
            <surname>Kim</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Lee</surname>
          </string-name>
          ,
          <string-name>
            <surname>POI GPT</surname>
          </string-name>
          :
          <article-title>Extracting POI Information from Social Media Text Data, The International Archives of the Photogrammetry</article-title>
          ,
          <source>Remote Sensing and Spatial Information Sciences XLVIII-4/W10- 2024</source>
          (
          <year>2024</year>
          )
          <fpage>113</fpage>
          -
          <lpage>118</lpage>
          . doi:
          <volume>10</volume>
          .5194/isprs-archives-XLVIII-4
          <string-name>
            <surname>-W10-</surname>
          </string-name>
          2024-113-
          <year>2024</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>C.</given-names>
            <surname>Berragan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Singleton</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Calafiore</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Morley</surname>
          </string-name>
          ,
          <article-title>Transformer based named entity recognition for place name extraction from unstructured text</article-title>
          ,
          <source>International Journal of Geographical Information Science</source>
          <volume>37</volume>
          (
          <year>2023</year>
          )
          <fpage>747</fpage>
          -
          <lpage>766</lpage>
          . doi:
          <volume>10</volume>
          .1080/13658816.
          <year>2022</year>
          .
          <volume>2133125</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M.</given-names>
            <surname>Stillman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Kruspe</surname>
          </string-name>
          ,
          <article-title>Geolocation Extraction From Reddit Text Data</article-title>
          , in: GeoExT 2024: Second International Workshop on Geographic Information Extraction from Texts at ECIR 2024, Glasgow Scotland, UK,
          <year>2024</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>K.</given-names>
            <surname>Stock</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. B.</given-names>
            <surname>Jones</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Russell</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Radke</surname>
          </string-name>
          ,
          <string-name>
            <surname>P. Das</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          <string-name>
            <surname>Aflaki</surname>
          </string-name>
          ,
          <article-title>Detecting geospatial location descriptions in natural language text</article-title>
          ,
          <source>International Journal of Geographical Information Science</source>
          <volume>36</volume>
          (
          <year>2022</year>
          )
          <fpage>547</fpage>
          -
          <lpage>584</lpage>
          . doi:
          <volume>10</volume>
          .1080/13658816.
          <year>2021</year>
          .
          <volume>1987441</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>C.</given-names>
            <surname>Loglisci</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Ienco</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Roche</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Teisseire</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Malerba</surname>
          </string-name>
          , Toward Geographic Information Harvesting:
          <article-title>Extraction of Spatial Relational Facts from Web Documents</article-title>
          ,
          <source>in: 2012 IEEE 12th International Conference on Data Mining Workshops</source>
          ,
          <string-name>
            <surname>IEEE</surname>
          </string-name>
          , Brussels, Belgium,
          <year>2012</year>
          , pp.
          <fpage>789</fpage>
          -
          <lpage>796</lpage>
          . doi:
          <volume>10</volume>
          .1109/ICDMW.
          <year>2012</year>
          .
          <volume>20</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>Q.</given-names>
            <surname>Qiu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Xie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Ma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Tao</surname>
          </string-name>
          ,
          <article-title>Spatially oriented convolutional neural network for spatial relation extraction from natural language texts</article-title>
          ,
          <source>Transactions in GIS 26</source>
          (
          <year>2022</year>
          )
          <fpage>839</fpage>
          -
          <lpage>866</lpage>
          . doi:
          <volume>10</volume>
          .1111/tgis.12887.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>H. M.</given-names>
            <surname>Rawsthorne</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Abadie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Kergosien</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Duchêne</surname>
          </string-name>
          , É. Saux,
          <article-title>Automatic Nested Spatial Entity and Spatial Relation Extraction From Text for Knowledge Graph Creation: A Baseline Approach and a Benchmark Dataset</article-title>
          ,
          <source>in: Proceedings of the 7th ACM SIGSPATIAL International Workshop on Geospatial Humanities</source>
          ,
          <string-name>
            <surname>ACM</surname>
          </string-name>
          , Hamburg Germany,
          <year>2023</year>
          , pp.
          <fpage>21</fpage>
          -
          <lpage>30</lpage>
          .
          <year>do1i</year>
          :
          <fpage>0</fpage>
          .1145/3615887. 3627754.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>Q.</given-names>
            <surname>Qiu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Xie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Ma</surname>
          </string-name>
          , L. Tao, S. Zheng,
          <article-title>NeuroSPE : A neuro-net spatial relation extractor for natural language text fusing gazetteers and pretrained models</article-title>
          ,
          <source>Transactions in GIS 27</source>
          (
          <year>2023</year>
          )
          <fpage>1526</fpage>
          -
          <lpage>1549</lpage>
          . doi:
          <volume>10</volume>
          .1111/tgis.13086.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>S.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Sun</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Ouyang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <source>GPT-NER: Named Entity Recognition via Large Language Models</source>
          ,
          <year>2023</year>
          . do1i:
          <fpage>0</fpage>
          .48550/ARXIV.2304.10428.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>X.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Zhu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <surname>N. Zhang,</surname>
          </string-name>
          <article-title>How to Unleash the Power of Large Language Models for Few-shot Relation Extraction?</article-title>
          ,
          <year>2023</year>
          . doi1:
          <fpage>0</fpage>
          .48550/ARXIV.2305.01555.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>X.</given-names>
            <surname>Hu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Kersten</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Klan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. M.</given-names>
            <surname>Farzana</surname>
          </string-name>
          ,
          <article-title>Toponym resolution leveraging lightweight and opensource large language models and geo-knowledge</article-title>
          ,
          <source>International Journal of Geographical Information Science</source>
          (
          <year>2024</year>
          )
          <fpage>1</fpage>
          -
          <lpage>28</lpage>
          . doi:
          <volume>10</volume>
          .1080/13658816.
          <year>2024</year>
          .
          <volume>2405182</volume>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>