<!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 />
    <article-meta>
      <title-group>
        <article-title>Using Large Language Models for Knowledge Engineering (LLMKE): A Case Study on Wikidata</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Bohui Zhang</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ioannis Reklos</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Nitisha Jain</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Albert Meroño Peñuela</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Elena Simperl</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Informatics, King's College London</institution>
          ,
          <addr-line>London</addr-line>
          ,
          <country country="UK">UK</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>In this work, we explore the use of Large Language Models (LLMs) for knowledge engineering tasks in the context of the ISWC 2023 LM-KBC Challenge. For this task, given subject and relation pairs sourced from Wikidata, we utilize pre-trained LLMs to produce the relevant objects in string format and link them to their respective Wikidata QIDs. We developed a pipeline using LLMs for Knowledge Engineering (LLMKE), combining knowledge probing and Wikidata entity mapping. The method achieved a macroaveraged F1-score of 0.701 across the properties, with the scores varying from 1.00 to 0.328. These results demonstrate that the knowledge of LLMs varies significantly depending on the domain and that further experimentation is required to determine the circumstances under which LLMs can be used for automatic Knowledge Base (e.g., Wikidata) completion and correction. The investigation of the results also suggests the promising contribution of LLMs in collaborative knowledge engineering. LLMKE won Track 2 of the challenge. The implementation is available at: https://github.com/bohuizhang/LLMKE.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Knowledge graphs (KGs) are a technology for knowledge representation and reasoning,
efectively transferring human intelligence into symbolic knowledge that machines can
comprehend and process [
        <xref ref-type="bibr" rid="ref7 ref8 ref9">7, 8, 9</xref>
        ]. The process of creating these KGs, referred to as knowledge
engineering, is not trivial, either automatically or collaboratively within human
communities [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. Wikidata [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], as the largest open KGs, contains rich knowledge of real-world entities.
It has been developed in a collaborative manner, with contributions from a community of users
and editors [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
      </p>
      <p>
        While the concept of using LMs to construct and complete KGs has been extensively explored
in previous research [
        <xref ref-type="bibr" rid="ref13 ref14 ref15">13, 14, 15</xref>
        ], the recent surge in LLMs performance has rekindled discussions
about the possibility of leveraging the strengths of both technologies and unifying them [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ].
Despite the immense potential ofered by LLMs as knowledge bases, there exist fundamental
disparities that diferentiate them from KGs. The most pivotal of these distinctions lies in
the domain of reasoning. Not only do traditional KGs store facts, they also impose logical
constraints on the entities and relations in terms of defining the types of the entities as well as
prescribing the domain and range of the relations. The capability of LLMs for logical reasoning
remains unclear and appears to face challenges [
        <xref ref-type="bibr" rid="ref17 ref18">17, 18</xref>
        ]. Moreover, the most widely adopted and
successful LLMs have been trained on data obtained from publicly available sources, and due to
the inherent limitations of the training method of these models, they tend to exhibit expert-level
knowledge in popular domains or entities while often displaying a limited understanding of
lesser-known ones.
      </p>
      <p>
        In this paper, we describe our approach LLMKE to using LLMs for Knowledge Engineering
tasks, especially targeting solving the ISWC 2023 LM-KBC Challenge [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ], and report our
ifndings regarding the prospect of using these models to improve the eficiency of knowledge
engineering. The task set by this challenge is to predict the object entities (zero or more)
given the subject entity and the relation that is sourced from Wikidata. For instance, given the
subject Robert Bosch LLC with Wikidata QID Q28973218 and the property
CompanyHasParentOrganisation, the task is to predict the list of object(s), [‘Robert Bosch’] and their matched
QID(s), [‘Q234021’]. We used two state-of-the-art LLMs, gpt-3.5-turbo4 and GPT-4 for this
task. By performing diferent experiments using in-context learning approaches, we have been
able to achieve a macro-average F1 score of 0.701, with F1-scores ranging from 0.3282 in the
PersonHasEmployer property to 1.0 in the PersonHasNobelPrize property.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Related Works</title>
      <sec id="sec-2-1">
        <title>2.1. LLMs for Knowledge Probing</title>
        <p>
          The ability of LLMs to perform knowledge-intensive tasks, especially knowledge probing, has
been extensively investigated [
          <xref ref-type="bibr" rid="ref20 ref21 ref22">20, 21, 22</xref>
          ]. In particular, several previous works have attempted
to use language models to construct or complete KGs. Among early works, the LAMA paper
by Petroni et al. [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ] investigated the task of knowledge graph completion by probing LMs
to extract facts via cloze-style prompts. Along similar lines, KG-BERT leverages the BERT
language model to perform the link prediction task for knowledge graph completion[
          <xref ref-type="bibr" rid="ref24">24</xref>
          ]. The
4https://platform.openai.com/docs/models/gpt-3-5
extent of the usefulness of LLMs for the construction and completion of knowledge graphs has
since been further analyzed [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. Follow up work after LAMA improved the performance even
further [
          <xref ref-type="bibr" rid="ref20 ref5">5, 20</xref>
          ]. Recently, Veseli et al. [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ] have performed a systematic analysis on the potential
of LMs for automated KG completion. They report that LMs can be useful for predicting facts
with high precision for some relations in Wikidata, though this is not generalizable. Prompt
engineering has caught the attention of many recent works that aim to elicit knowledge from
the language models [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]. These works are the most similar to our approach in this paper.
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Knowledge Probing Benchmarks</title>
        <p>
          To fulfil the need for comprehensively investigating the ability of LLMs to perform
knowledgeintensive tasks, there has been a growing trend of knowledge-oriented benchmarks and datasets.
These benchmarks encompass diverse domains, address various scenarios, including question
answering, reading comprehension, and fact completion, and represent knowledge in diferent
formats, including queries, cloze-style, incomplete triples, etc [
          <xref ref-type="bibr" rid="ref21 ref25">21, 25</xref>
          ]. And knowledge graphs,
especially the large-scale and general-purpose ones, have become vital sources for constructing
these benchmarks. As the pioneering dataset in the language models era, LAMA was constructed
from a variety of knowledge graph sources of factual and commonsense knowledge, including
T-REx [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ], ConceptNet [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ], etc. There are several benchmarks that evolved from it to overcome
its limitations and expand its abilities, such as KAMEL [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ] which extended LAMA from
singletoken objects to multi-token ones. KILT [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ] was constructed from millions of Wikipedia pages
spanning a wide range of knowledge-intensive language tasks. WikiFact [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ] as a part of the
HELM benchmark is the most similar to this challenge, where they use Wikidata relations and
triples to construct the benchmark. But the challenge used a diferent evaluation paradigm.
KoLA [
          <xref ref-type="bibr" rid="ref30">30</xref>
          ] aimed at measuring the real-world performance of LLMs by expanding beyond
language modeling, adding evolving data sources, and attempting to measure the ability of
the models in all facets of knowledge processing, ranging from knowledge memorization to
knowledge creation. The data sources it used are also highly overlapping with Wikidata and
Wikipedia.
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Methods</title>
      <sec id="sec-3-1">
        <title>3.1. Problem Formulation</title>
        <p>Most of the previous works on using LLMs for fact completion stop at the string level, which
leaves gaps for constructing hands-on knowledge graphs and thus hinders downstream
application. Our work pushed a step forward on this task, where the extracted knowledge is not only
in string format but also linked to their respective Wikidata entities. Formally, given a query
consisting of subject entity  and relation , the task is to predict a set of objects {} with
unknown numbers (|{}| ≥ 0) by prompting LLMs and mapping the objects to their related
Wikidata entities { , · · · ,  }.</p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. The LLMKE Pipeline</title>
        <sec id="sec-3-2-1">
          <title>3.2.1. Knowledge Probing</title>
          <p>The pipeline consists of two steps: knowledge probing and Wikidata entity mapping. For
the knowledge probing step, we engineered prompt templates for probing knowledge from
LLMs. We adopt OpenAI’s gpt-3.5-turbo and GPT-4 in this step. For each of the LLMs, we run
experiments with three types of settings. The first is question prompting, where LLMs are
provided with questions as queries. For example, “Which countries share borders with Brazil?".
The second is triple completion prompting, where prompts are formatted as incomplete triples,
such as “River Thames, RiverBasinsCountry:”. There are several heuristics employed in these
two settings. For example, there are only 5 diferent Nobel Prizes, so PersonHasNobelPrize has 6
candidate answers, including the empty answer. When the answer space is limited, providing
all potential answers in the prompt templates is likely to reduce the dificulty of formatting and
disambiguating the objects, thus helping LLMs perform well.</p>
          <p>In the third setting, we provide retrieval-augmented context to help LLMs by enriching
knowledge from corpus, including Wikipedia and domain-specific websites. Trying to leave
space for invoking the ‘critical thinking’ of LMs and for further investigating the efect of
adding context, the prompts used in this setting are separated into two steps. At first, we ask
LLMs to predict the objects based on their own knowledge using the same settings as question
prompting. In the second step, we provided the context knowledge, and LLMs were asked to
make predictions again by considering the context and comparing it with the previous response.
The prompt is like ‘Given the context: [retrieval-augmented context], compared and combined
with the previous predictions, [question prompt]’. In this case, we let LLMs to decide whether
they will insist on their own knowledge or change their answers based on the context. In this
study, we used Wikipedia as the general-domain context source. The first paragraphs of the
entity’s Wikipedia page (the introduction) and the JSON format of the Wikipedia Infobox are
organized and provided to LLMs. For relations that could potentially have empty results, the
prompt indicated the required return format (i.e., [""]).</p>
          <p>In all settings, we perform few-shot learning, where we provide three examples (i.e., prompt
and answer pairs) from the training set. Since the required format of results is a list, providing
examples with the exact format is expected to help LLMs return better-formatted results.</p>
        </sec>
        <sec id="sec-3-2-2">
          <title>3.2.2. Wikidata Entity Mapping</title>
          <p>The entity mapping step first finds Wikidata entities for each object string using the MediaWiki
Action API5. One of the actions, wbsearchentities6 which searches for entities using labels and
aliases, returns all possible Wikidata entities as candidates. Then, in the disambiguation step,
the actual Wikidata entities linked to the objects are selected. The baseline disambiguation
method selects the first entity from the list of candidates returned by the wbsearchentities action,
which is notably incorrect. To reduce the cost while improving the accuracy for disambiguation,
we treated diferent relations with three improved methods: case-based, keyword-based, and
LM-based.</p>
          <p>5https://www.wikidata.org/w/api.php
6https://www.wikidata.org/w/api.php?action=help&amp;modules=wbsearchentities</p>
          <p>The case-based method is a hard-coding solution for eficiently solving ambiguities for
relations with smaller answer spaces and limited corner cases. It is built on the baseline method
by adding the function that maps specific objects to their respective Wikidata QIDs. For example,
CompoundHasParts only has all the chemical elements as its answer space. Further, there is only
one mistake in the baseline method, ‘mercury’. Thus, when predicting for CompoundHasParts,
the case-based method always maps ‘mercury’ in the object lists to Q925 (the chemical element
with symbol Hg) instead of Q308 (the planet). For other relations with a larger answer space but
also entities with common characteristics, we used the keyword-based method, which extracts
the description of the candidate entities from its Wikidata page and searches entities with their
description using relevant keywords. This method is used when there are common words in
the entity description. For example, object entities of the relation CountryHasOficialLanguage
always have the keyword ‘language’ in their descriptions.</p>
          <p>The above two methods clearly sufer from limitations due to their poor coverage and
inflexibility. The third method is language model-based ( LM-based). We constructed a dictionary
of all candidate QIDs with their labels as keys and descriptions as values, concatenated it with the
query in this first step, and asked LMs to determine which one should be selected. This method
is used when there is no semantic commonality between the answers and disambiguation is
required to understand the diference between entities, e.g., properties with the whole range
of human beings as potential answers such as ‘PersonHasSpouse’. As there is no commonality
among the labels and descriptions of answers, the decision is left to the LMs. This method also
has limitations, such as being time-consuming and unstable.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Results</title>
      <sec id="sec-4-1">
        <title>4.1. Datasets</title>
        <p>
          The dataset used in the ISWC 2023 LM-KBC Challenge [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ] is queried from Wikidata and
further processed. It comprises 21 Wikidata relation types that cover 7 domains, including
music, television series, sports, geography, chemistry, business, administrative divisions, and
public figure information. It has 1,940 statements for each train, validation, and test sets. The
results reported are based on the test set.7 In the dataset, the minimum and maximum number
of object-entities for each relation is diferent, ranging from 0 to 20. The minimum number of 0
means the subject-entities for some relations can have zero valid object-entities, for example,
people still alive should not have a place or cause of death.
        </p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Model Performance</title>
        <p>In terms of the overall performance of the model as shown in Table 1 and 3, GPT-4 is better than
gpt-3.5-turbo. The retrieval-augmented context setting has the best performance compared
with the other two few-shot learning settings. And the performance on question answering
prompts and triple completion prompts is quite close.</p>
        <p>7To investigate the actual knowledge gap between LLMs and Wikidata, we created ground truths of the test set
through Wikidata SPARQL queries for ofline evaluation. We report and analyze the ofline evaluation results in
Section 4 and the online evaluation results from CodaLab in Appendix A.</p>
        <p>From the lens of relations, as shown in the detailed results of GPT-4 (Table 2), LLMs perform
well when the relation has a limited domain and/or range, for example, PersonHasNobelPrize,
CountryHasOficialLanguage , and CompoundHasParts. On the other hand, LLMs perform poorly
for relations such as PersonHasEmployer, PersonHasProfession, and PersonHasAutobiography.
This may be due to two reasons: firstly, LLMs have limited knowledge about public figures
and their personal information (except for famous ones). Secondly, the unlimited answer space
for such relations could increase the dificulty of prediction. The results show that LLMs
perform relatively well on the knowledge of geography, as GPT-4 achieved F1-scores of 0.629
on CityLocatedAtRiver, 0.763 on CountryBordersCountry, 0.855 on RiverBasinsCountry, and 0.581
on StateBordersState, and the performance is inversely correlated with the size of the object
range. The knowledge of public figures contained in LLMs could be an interesting topic to
investigate since their performance across diferent aspects varies significantly. While LLMs
correctly handle every instance of PersonHasNobelPrize, they also demonstrate relatively strong
performance in areas such as place of birth and death, cause of death, and spouses. However,
their performance tends to be deficient when it comes to details about individuals’ employers
and professions.</p>
      </sec>
      <sec id="sec-4-3">
        <title>4.3. Retrieval-Augmented Prediction</title>
        <p>
          Providing relevant corpus as context to LLMs is an established method for improving model
performance [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ]. As such, we experimented with various sources and forms of context and
selected the best ones for each relation. In particular, we experimented with using the
introduction paragraphs of the Wikipedia article for the subject entity, the Infobox of the Wikipedia
article for the subject entity in JSON format, as well as relation-specific sources such as IMDb.
The efect of providing context varies for diferent models. It is observed gpt-3.5-turbo benefits
from the context more compared with GPT-4. Reflected from F1-scores, the retrieval-augmented
context setting exhibits an improvement of 0.055 compared with the question prompting setting
for gpt-3.5-turbo and 0.004 for GPT-4.
        </p>
        <p>In contrast to our intuition, adding context knowledge does not enhance the performance
of GPT-4 in all relations as compared to only proving the few-shot examples, where only 10
out of 21 relations achieved better results in the context setting compared to the question and
triple settings. Several factors may contribute to this, including the presence of a knowledge
relations, where we augmented relation-specific context. For the
SeriesHasNumberOfEpisodes
relation, except for the previous two sources, we augmented the context from IMDb. The
information on IMDb was added to the prompt prefaced by the label “IMDb”, and the model
was asked to use this information (if it was available) to provide an answer. Moreover, for the
CountryHasState relation, we discovered that GPT-4 would treat ‘state’ more like the definition
of ‘country’ than that of the administrative division entity. Therefore, we experimented with
providing the model with “Administrative Division of [entity]” Wikipedia page content, which
outperformed the question setting for 0.007 of the F1-score.</p>
      </sec>
      <sec id="sec-4-4">
        <title>4.4. Disambiguation</title>
        <p>When using the baseline disambiguation method, we observed disambiguation mistakes in
13 relations. These errors are categorized into two groups: surface disambiguation errors,
in which the model produced the same strings of entities as the ground truths but assigned
incorrect QIDs, and deep disambiguation errors, where the model associated the same entities
with diferent names (i.e., aliases) and also assigned incorrect QIDs. In this study, we focus
only on addressing the former category while reserving discussion of the latter for future
research. To tackle this challenge, we implemented improved disambiguation methods with
the dual objective of rectifying errors to the fullest extent possible and concurrently reducing
computational complexity.</p>
        <p>From Table 1, we can observe an average increase in F1-scores of 0.0256 for all settings in the
case of gpt-3.5-turbo and 0.0289 for GPT-4. For the 13 relations where improved disambiguation
methods are applied, Table 2 listed the best-performing disambiguation method for each relation.
Notably, for 3 relations (CompoundHasParts, PersonPlaysInstrument, and RiverBasinsCountry),
the issues have been successfully solved. However, the rest 8 relations still remain either 2 or
fewer unsolved errors, and 2 relations (BandHasMember and StateBordersState) face more than 7
unsolved errors, exceeding the capacity of their respective methods.</p>
        <p>Given that the wbsearchentities Action API relies on label and alias-based searching, there’s a
potential issue when LLMs predict objects with labels that are absent from the label and aliases
of the corresponding Wikidata entity. This mismatch can lead to an incomplete list of candidate
entities. From this perspective, LLMs have the ability to contribute to knowledge engineering
by enriching the labels and aliases associated with Wikidata entities.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Discussion</title>
      <sec id="sec-5-1">
        <title>5.1. Wikidata Quality</title>
        <p>
          During the development of our pipeline and the evaluation of the results, it became apparent
that the quality of Wikidata is an important issue, a problem that has also been discussed
in previous works [
          <xref ref-type="bibr" rid="ref32 ref33">32, 33</xref>
          ]. For example, a large number of elements are missing for the
relation CompoundHasParts, and many objects violate the value-type constraint of properties.
In this situation, our proposed method would be useful for automatically providing suggestions
and candidates for incomplete triples and thus enriching Wikidata by improving its quality.
Moreover, it is possible to use LLMs to align the knowledge contained in Wikidata with the
knowledge contained in Wikipedia and complete the triples of Wikidata using the Wikipedia
articles as context. Furthermore, the performance of the LLMs on the object prediction task
can be used as a metric to gauge the completeness of Wikidata entities. In cases where the
diference between the predictions of the LLMs and the ground truth is substantial, the entity
can be suggested to Wikidata editors for review using a recommender system, such as the one
described by [
          <xref ref-type="bibr" rid="ref34">34</xref>
          ]. Finally, the labels (synonyms) of Wikidata entities are incomplete, which
limits the ability of our disambiguation method since the system that retrieves the candidate
entities needs labels and aliases to match the given string.
        </p>
      </sec>
      <sec id="sec-5-2">
        <title>5.2. Knowledge Gap</title>
        <p>Through our eforts to use Wikipedia as relevant context to improve the performance of LLMs
in the object prediction task, we observed a significant knowledge gap between Wikipedia and
Wikidata, which caused the performance of the model to deteriorate when provided with context
sourced from Wikipedia for some of the relations. To elucidate the cause of this phenomenon,
we manually inspected several of these instances and realized that the information contained in
Wikidata is diferent from the information contained in Wikipedia. One such example is the
subject-relation pair Ferrari S.p.A., CompanyHasParentOrganisation, for which LLMs correctly
predicted the object Exor, matching the information on Wikipedia and the oficial report from
Ferrari in 2021, whereas Wikidata contains the object Ferrari N.V., which is outdated. This
knowledge gap between Wikipedia and Wikidata is an open issue, and LLMs, either alone or
by supporting human editors and suggesting edits, could play a pivotal role in addressing this
issue and improving the data quality and recency of information contained in Wikidata. Finally,
the knowledge gap is not limited to Wikidata and Wikipedia but appears to exist between LLMs
as well. Specifically, as seen in Table 3, gpt-3.5-turbo outperforms the larger GPT-4 in two
of the relations. Based on this, it stands to reason that diferent LLMs can contain diferent
knowledge, and therefore, using an ensemble of LLMs with complementary strengths can lead
to an improvement in performance.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusion</title>
      <p>Within the scope of the ISWC 2023 LM-KBC challenge, this work aimed at developing a method to
probe LLMs for predicting the objects of Wikidata triples given the subject and relation. Our
bestperforming method achieved state-of-the-art results with a macro-averaged F1-score of 0.7007
across all relations, with GPT-4 having the best performance on the PersonHasNobelPrize relation
and achieving a score of 1.0, while only achieving a score of 0.328 on the PersonHasEmployer
relation. These results show that LLMs can be efectively used to complete knowledge bases
when used in the appropriate context. At the same time, it is important to note that, largely
due to the gaps in their knowledge, fully automatic knowledge engineering using LLMs is
not currently possible for all domains, and a human-in-the-loop is still required to ensure the
accuracy of the information.</p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgments</title>
      <p>This work was partly funded by the HE project MuseIT, which has been co-founded by the
European Union under the Grant Agreement No 101061441. Views and opinions expressed are,
however, those of the authors and do not necessarily reflect those of the European Union or
European Research Executive Agency.</p>
    </sec>
    <sec id="sec-8">
      <title>A. Online Evaluation Results</title>
    </sec>
    <sec id="sec-9">
      <title>B. Prompt Templates</title>
      <p>BandHasMember
Who are the members of {subject_entity}? Format the response as a Python list such as
["answer_a", "answer_b"].</p>
      <p>CityLocatedAtRiver
Which river is {subject_entity} located at? Format the response as a Python list such as
["answer_a", "answer_b"].</p>
      <p>CompanyHasParentOrganisation
{subject_entity} is a subsidiary of which company? Return a Python list with an empty string
(i.e. [""]) if none. Format the response as a Python list such as ["answer_a", "answer_b"].
CountryBordersCountry
Which countries share borders with {subject_entity}? Format the response as a Python list such
as ["answer_a", "answer_b"].</p>
      <p>CountryHasOficialLanguage
What is the oficial language of {subject_entity}? Format the response as a Python list such as
["answer_a", "answer_b"].</p>
      <p>CountryHasStates
What are the first-level administrative territorial entities of {subject_entity}? Format the
response as a Python list such as ["answer_a", "answer_b"].</p>
      <p>FootballerPlaysPosition
What position does {subject_entity} play in football? Format the response as a Python list such
as ["answer_a", "answer_b"].</p>
      <p>PersonCauseOfDeath
What caused the death of {subject_entity}? If none or still alive, return [""]. Format the response
as a Python list such as ["answer_a", "answer_b"].</p>
      <p>PersonHasAutobiography
What is the title of {subject_entity}’s autobiography? Format the response as a Python list such
as ["answer_a", "answer_b"].</p>
      <p>PersonHasEmployer
Who is {subject_entity}’s employer? Format the response as a Python list such as ["answer_a",
"answer_b"].</p>
      <p>PersonHasNoblePrize
Which Nobel Prize did {subject_entity} receive? Select from this list: ["Nobel Peace Prize",
"Nobel Prize in Literature", "Nobel Prize in Physics", "Nobel Prize in Chemistry", "Nobel Prize in
Physiology or Medicine"]. Return a Python list with an empty string (i.e. [""]) if none. Format
the response as a Python list such as ["answer_a", "answer_b"].</p>
      <p>PersonHasNumberOfChildren
How many children does {subject_entity} have? Return the string format of the number only.
Format the response as a Python list such as ["answer_a", "answer_b"].</p>
      <p>PersonHasPlaceOfDeath
Where did {subject_entity} die? Return a Python list with an empty string (i.e. [""]) if he or she
is still alive. Format the response as a Python list such as ["answer_a", "answer_b"].
PersonHasProfession
What is {subject_entity}’s profession or occupation? Format the response as a Python list such
as ["answer_a", "answer_b"].</p>
      <p>PersonHasSpouse
What is the name of the spouse of {subject_entity}? Format the response as a Python list such
as ["answer_a", "answer_b"].</p>
      <p>PersonPlaysInstrument
What instruments does {subject_entity} play? Format the response as a Python list such as
["answer_a", "answer_b"].</p>
      <p>PersonSpeaksLanguage
What languages does {subject_entity} speak? Format the response as a Python list such as
["answer_a", "answer_b"].</p>
      <p>RiverBasinsCountry
In which country can you find the {subject_entity} river basin? Format the response as a Python
list such as ["answer_a", "answer_b"].</p>
      <p>SeriesHasNumberOfEpisodes
How many episodes does the series {subject_entity} have? Return the string format of the
number. Format the response as a Python list such as ["answer_a", "answer_b"].
CompoundHasParts
What are the chemical components of {subject_entity}? Return the full name of components such
as ["carbon", "nitrogen"]. Format the response as a Python list such as ["answer_a", "answer_b"].
StateBordersState
Which states border the state of {subject_entity}? Format the response as a Python list such as
["answer_a", "answer_b"].</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1] OpenAI, GPT-4
          <source>Technical Report</source>
          ,
          <year>2023</year>
          . arXiv:
          <volume>2303</volume>
          .
          <fpage>08774</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>H.</given-names>
            <surname>Touvron</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Lavril</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Izacard</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Martinet</surname>
          </string-name>
          , M.
          <article-title>-</article-title>
          <string-name>
            <surname>A. Lachaux</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Lacroix</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <string-name>
            <surname>Rozière</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          <string-name>
            <surname>Goyal</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <string-name>
            <surname>Hambro</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          <string-name>
            <surname>Azhar</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Rodriguez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Joulin</surname>
            , E. Grave, G. Lample, LLaMA: Open and
            <given-names>Eficient</given-names>
          </string-name>
          <string-name>
            <surname>Foundation Language Models</surname>
          </string-name>
          ,
          <year>2023</year>
          . arXiv:
          <volume>2302</volume>
          .
          <fpage>13971</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>H.</given-names>
            <surname>Touvron</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Martin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Stone</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Albert</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Almahairi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Babaei</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Bashlykov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Batra</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Bhargava</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Bhosale</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Bikel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Blecher</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. C.</given-names>
            <surname>Ferrer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Cucurull</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Esiobu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Fernandes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Fu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Fu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Fuller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Gao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Goswami</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Goyal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Hartshorn</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Hosseini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Hou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Inan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Kardas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Kerkez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Khabsa</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Kloumann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Korenev</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. S.</given-names>
            <surname>Koura</surname>
          </string-name>
          , M.
          <article-title>-</article-title>
          <string-name>
            <surname>A. Lachaux</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Lavril</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Liskovich</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          <string-name>
            <surname>Lu</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          <string-name>
            <surname>Mao</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          <string-name>
            <surname>Martinet</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Mihaylov</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Mishra</surname>
            , I. Molybog,
            <given-names>Y.</given-names>
          </string-name>
          <string-name>
            <surname>Nie</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Poulton</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Reizenstein</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Rungta</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Saladi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Schelten</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Silva</surname>
            ,
            <given-names>E. M.</given-names>
          </string-name>
          <string-name>
            <surname>Smith</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Subramanian</surname>
            ,
            <given-names>X. E.</given-names>
          </string-name>
          <string-name>
            <surname>Tan</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <string-name>
            <surname>Tang</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Taylor</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Williams</surname>
            ,
            <given-names>J. X.</given-names>
          </string-name>
          <string-name>
            <surname>Kuan</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Xu</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          <string-name>
            <surname>Yan</surname>
            , I. Zarov,
            <given-names>Y.</given-names>
          </string-name>
          <string-name>
            <surname>Zhang</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Fan</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Kambadur</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Narang</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Rodriguez</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Stojnic</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Edunov</surname>
          </string-name>
          ,
          <source>T. Scialom, Llama</source>
          <volume>2</volume>
          :
          <string-name>
            <given-names>Open</given-names>
            <surname>Foundation</surname>
          </string-name>
          and
          <string-name>
            <surname>Fine-Tuned Chat</surname>
            <given-names>Models</given-names>
          </string-name>
          ,
          <year>2023</year>
          . arXiv:
          <volume>2307</volume>
          .
          <fpage>09288</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>T.</given-names>
            <surname>Shin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Razeghi</surname>
          </string-name>
          , R. L.
          <string-name>
            <surname>Logan</surname>
            <given-names>IV</given-names>
          </string-name>
          , E. Wallace, S. Singh,
          <article-title>AutoPrompt: Eliciting Knowledge from Language Models with Automatically Generated Prompts</article-title>
          ,
          <source>in: Proceedings of the 2020 Conference on Empirical Methods in Natural Language Processing (EMNLP)</source>
          ,
          <article-title>Association for Computational Linguistics</article-title>
          , Online,
          <year>2020</year>
          , pp.
          <fpage>4222</fpage>
          -
          <lpage>4235</lpage>
          . URL: https://aclanthology.org/
          <year>2020</year>
          .emnlp-main.
          <volume>346</volume>
          . doi:
          <volume>10</volume>
          .18653/v1/
          <year>2020</year>
          .emnlp-main.
          <volume>346</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>G.</given-names>
            <surname>Qin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Eisner</surname>
          </string-name>
          , Learning How to Ask:
          <article-title>Querying LMs with Mixtures of Soft Prompts, in: Proceedings of the 2021 Conference of the North American Chapter of the Association for Computational Linguistics: Human Language Technologies, Association for Computational Linguistics</article-title>
          , Online,
          <year>2021</year>
          , pp.
          <fpage>5203</fpage>
          -
          <lpage>5212</lpage>
          . URL: https://aclanthology.org/
          <year>2021</year>
          .naacl-main.
          <volume>410</volume>
          . doi:
          <volume>10</volume>
          .18653/v1/
          <year>2021</year>
          .naacl-main.
          <volume>410</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>P.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Yuan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Fu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Jiang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Hayashi</surname>
          </string-name>
          , G. Neubig, Pre-Train, Prompt, and
          <article-title>Predict: A Systematic Survey of Prompting Methods in Natural Language Processing</article-title>
          ,
          <source>ACM Comput. Surv</source>
          .
          <volume>55</volume>
          (
          <year>2023</year>
          ). URL: https://doi.org/10.1145/3560815. doi:
          <volume>10</volume>
          .1145/3560815.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>L.</given-names>
            <surname>Ehrlinger</surname>
          </string-name>
          , W. Wöß,
          <article-title>Towards a Definition of Knowledge Graphs, SEMANTiCS (Posters</article-title>
          , Demos, SuCCESS)
          <volume>48</volume>
          (
          <year>2016</year>
          )
          <article-title>2</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>D.</given-names>
            <surname>Fensel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>U.</given-names>
            <surname>Simsek</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Angele</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Huaman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Karle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Panasiuk</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Toma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Umbrich</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Wahler</surname>
          </string-name>
          , Knowledge Graphs: Methodology, Tools and Selected Use Cases, 1st ed., Springer Publishing Company, Incorporated,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>A.</given-names>
            <surname>Hogan</surname>
          </string-name>
          , E. Blomqvist,
          <string-name>
            <given-names>M.</given-names>
            <surname>Cochez</surname>
          </string-name>
          , C. d'Amato, G. de Melo,
          <string-name>
            <given-names>C.</given-names>
            <surname>Gutierrez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Kirrane</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Gayo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Navigli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Neumaier</surname>
          </string-name>
          , et al.,
          <string-name>
            <surname>Knowledge</surname>
            <given-names>Graphs</given-names>
          </string-name>
          ,
          <source>Synthesis Lectures on Data, Semantics, and Knowledge</source>
          , Morgan &amp; Claypool Publishers,
          <year>2021</year>
          . URL: https://books. google.co.uk/books?id=hJ1NEAAAQBAJ.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>U.</given-names>
            <surname>Simsek</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Kärle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Angele</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Huaman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Opdenplatz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Sommer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Umbrich</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Fensel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A Knowledge</given-names>
            <surname>Graph</surname>
          </string-name>
          <article-title>Perspective on Knowledge Engineering, SN Comput</article-title>
          .
          <source>Sci. 4</source>
          (
          <year>2022</year>
          ). URL: https://doi.org/10.1007/s42979-022-01429-x. doi:
          <volume>10</volume>
          .1007/s42979-022-01429-x.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>D.</given-names>
            <surname>Vrandečić</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Krötzsch</surname>
          </string-name>
          , Wikidata:
          <string-name>
            <given-names>A Free</given-names>
            <surname>Collaborative</surname>
          </string-name>
          <string-name>
            <surname>Knowledgebase</surname>
          </string-name>
          ,
          <source>Commun. ACM</source>
          <volume>57</volume>
          (
          <year>2014</year>
          )
          <fpage>78</fpage>
          -
          <lpage>85</lpage>
          . URL: https://doi.org/10.1145/2629489. doi:
          <volume>10</volume>
          .1145/2629489.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>A.</given-names>
            <surname>Piscopo</surname>
          </string-name>
          , E. Simperl, Who Models the World?
          <article-title>Collaborative Ontology Creation and User Roles in Wikidata</article-title>
          ,
          <source>Proc. ACM Hum.-Comput. Interact</source>
          .
          <volume>2</volume>
          (
          <year>2018</year>
          ). URL: https://doi.org/ 10.1145/3274410. doi:
          <volume>10</volume>
          .1145/3274410.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>S.</given-names>
            <surname>Razniewski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Yates</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Kassner</surname>
          </string-name>
          ,
          <string-name>
            <surname>G.</surname>
          </string-name>
          <article-title>Weikum, Language Models As or For Knowledge Bases</article-title>
          ,
          <source>CoRR abs/2110</source>
          .04888 (
          <year>2021</year>
          ). URL: https://arxiv.org/abs/2110.04888. arXiv:
          <volume>2110</volume>
          .
          <fpage>04888</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>D.</given-names>
            <surname>Alivanistos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Santamaría</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Cochez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Kalo</surname>
          </string-name>
          , E. van Krieken,
          <string-name>
            <given-names>T.</given-names>
            <surname>Thanapalasingam</surname>
          </string-name>
          ,
          <article-title>Prompting as Probing: Using Language Models for Knowledge Base Construction</article-title>
          , in: S. Singhania,
          <string-name>
            <given-names>T.-P.</given-names>
            <surname>Nguyen</surname>
          </string-name>
          , S. Razniewski (Eds.),
          <article-title>LM-KBC 2022 Knowledge Base Construction from Pre-trained</article-title>
          <source>Language Models</source>
          <year>2022</year>
          , CEUR Workshop Proceedings, CEUR-WS.org,
          <year>2022</year>
          , pp.
          <fpage>11</fpage>
          -
          <lpage>34</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>B.</given-names>
            <surname>Veseli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Singhania</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Razniewski</surname>
          </string-name>
          ,
          <string-name>
            <surname>G.</surname>
          </string-name>
          <article-title>Weikum, Evaluating Language Models For Knowledge Base Completion</article-title>
          , in: The Semantic Web: 20th International Conference, ESWC 2023, Hersonissos, Crete, Greece, May 28-June 1,
          <year>2023</year>
          , Proceedings, Springer-Verlag, Berlin, Heidelberg,
          <year>2023</year>
          , p.
          <fpage>227</fpage>
          -
          <lpage>243</lpage>
          . URL: https://doi.org/10.1007/978-3-
          <fpage>031</fpage>
          -33455-9_
          <fpage>14</fpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>031</fpage>
          -33455-9_
          <fpage>14</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>S.</given-names>
            <surname>Pan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Luo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <source>Unifying Large Language Models and Knowledge Graphs: A Roadmap</source>
          ,
          <source>arXiv preprint arxiv:306.08302</source>
          (
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>J.</given-names>
            <surname>Wei</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Schuurmans</surname>
          </string-name>
          , M. Bosma, brian ichter,
          <string-name>
            <given-names>F.</given-names>
            <surname>Xia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E. H.</given-names>
            <surname>Chi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Q. V.</given-names>
            <surname>Le</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Zhou</surname>
          </string-name>
          ,
          <article-title>Chain of Thought Prompting Elicits Reasoning in Large Language Models</article-title>
          , in: A. H.
          <string-name>
            <surname>Oh</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Agarwal</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Belgrave</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          Cho (Eds.),
          <source>Advances in Neural Information Processing Systems</source>
          ,
          <year>2022</year>
          . URL: https://openreview.net/forum?id=_VjQlMeSB_J.
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>J.</given-names>
            <surname>Huang</surname>
          </string-name>
          ,
          <string-name>
            <surname>K. C.-C. Chang</surname>
          </string-name>
          ,
          <article-title>Towards Reasoning in Large Language Models: A Survey, in: Findings of the Association for Computational Linguistics: ACL 2023, Association for Computational Linguistics</article-title>
          , Toronto, Canada,
          <year>2023</year>
          , pp.
          <fpage>1049</fpage>
          -
          <lpage>1065</lpage>
          . URL: https: //aclanthology.org/
          <year>2023</year>
          .findings-acl.
          <volume>67</volume>
          . doi:
          <volume>10</volume>
          .18653/v1/
          <year>2023</year>
          .findings-acl.
          <volume>67</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>S.</given-names>
            <surname>Singhania</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.-C.</given-names>
            <surname>Kalo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Razniewski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. Z.</given-names>
            <surname>Pan</surname>
          </string-name>
          ,
          <article-title>LM-KBC: Knowledge base construction from pre-trained language models</article-title>
          ,
          <source>Semantic Web Challenge @ ISWC</source>
          ,
          <string-name>
            <surname>CEUR-WS</surname>
          </string-name>
          (
          <year>2023</year>
          ). URL: https://lm-kbc.
          <source>github.io/challenge2023.</source>
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Zhong</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Friedman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Chen</surname>
          </string-name>
          , Factual Probing Is [MASK]
          <article-title>: Learning vs. Learning to Recall, in: Proceedings of the 2021 Conference of the North American Chapter of the Association for Computational Linguistics: Human Language Technologies, Association for Computational Linguistics</article-title>
          , Online,
          <year>2021</year>
          , pp.
          <fpage>5017</fpage>
          -
          <lpage>5033</lpage>
          . URL: https://aclanthology.org/
          <year>2021</year>
          .naacl-main.
          <volume>398</volume>
          . doi:
          <volume>10</volume>
          .18653/v1/
          <year>2021</year>
          .naacl-main.
          <volume>398</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>P.</given-names>
            <surname>Liang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Bommasani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Lee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Tsipras</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Soylu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Yasunaga</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Narayanan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Kumar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Newman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Yuan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Yan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Cosgrove</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. D.</given-names>
            <surname>Manning</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Ré</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Acosta-Navas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. A.</given-names>
            <surname>Hudson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Zelikman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Durmus</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Ladhak</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Rong</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Ren</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Yao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Santhanam</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Orr</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Zheng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Yuksekgonul</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Suzgun</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Kim</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Guha</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Chatterji</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Khattab</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Henderson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Q.</given-names>
            <surname>Huang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Chi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. M.</given-names>
            <surname>Xie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Santurkar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Ganguli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Hashimoto</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Icard</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Chaudhary</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Mai</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , Y. Koreeda,
          <source>Holistic Evaluation of Language Models</source>
          ,
          <year>2022</year>
          . arXiv:
          <volume>2211</volume>
          .
          <fpage>09110</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>H.</given-names>
            <surname>Peng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Hu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Jin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Hou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Liu</surname>
          </string-name>
          , Q. Liu, COPEN:
          <article-title>Probing Conceptual Knowledge in Pre-trained Language Models</article-title>
          ,
          <source>in: Proceedings of EMNLP</source>
          ,
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>F.</given-names>
            <surname>Petroni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Rocktäschel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Riedel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Lewis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Bakhtin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Miller</surname>
          </string-name>
          ,
          <article-title>Language Models as Knowledge Bases?</article-title>
          ,
          <source>in: Proceedings of the 2019 Conference on Empirical Methods in Natural Language Processing and the 9th International Joint Conference on Natural Language Processing (EMNLP-IJCNLP)</source>
          ,
          <article-title>Association for Computational Linguistics</article-title>
          , Hong Kong, China,
          <year>2019</year>
          , pp.
          <fpage>2463</fpage>
          -
          <lpage>2473</lpage>
          . URL: https://aclanthology.org/D19-1250. doi:
          <volume>10</volume>
          . 18653/v1/
          <fpage>D19</fpage>
          -1250.
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>L.</given-names>
            <surname>Yao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Mao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Luo</surname>
          </string-name>
          , KG-BERT:
          <article-title>BERT for Knowledge Graph Completion</article-title>
          , CoRR abs/
          <year>1909</year>
          .03193 (
          <year>2019</year>
          ). URL: http://arxiv.org/abs/
          <year>1909</year>
          .03193. arXiv:
          <year>1909</year>
          .03193.
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>A.</given-names>
            <surname>Rogers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Gardner</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Augenstein</surname>
          </string-name>
          , QA Dataset Explosion:
          <article-title>A Taxonomy of NLP Resources for Question Answering</article-title>
          and Reading Comprehension,
          <source>ACM Comput. Surv</source>
          .
          <volume>55</volume>
          (
          <year>2023</year>
          ). URL: https://doi.org/10.1145/3560260. doi:
          <volume>10</volume>
          .1145/3560260.
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <given-names>H.</given-names>
            <surname>Elsahar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Vougiouklis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Remaci</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Gravier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Hare</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Laforest</surname>
          </string-name>
          , E. Simperl,
          <string-name>
            <surname>T-REx: A Large Scale</surname>
          </string-name>
          <article-title>Alignment of Natural Language with Knowledge Base Triples</article-title>
          ,
          <source>in: Proceedings of the Eleventh International Conference on Language Resources and Evaluation (LREC</source>
          <year>2018</year>
          ),
          <article-title>European Language Resources Association (ELRA), Miyazaki</article-title>
          , Japan,
          <year>2018</year>
          . URL: https://aclanthology.org/L18-1544.
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [27]
          <string-name>
            <given-names>R.</given-names>
            <surname>Speer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Havasi</surname>
          </string-name>
          , Representing
          <article-title>General Relational Knowledge in ConceptNet 5</article-title>
          , in: Proceedings of the Eighth International Conference on
          <article-title>Language Resources and Evaluation (LREC'12), European Language Resources Association (ELRA</article-title>
          ), Istanbul, Turkey,
          <year>2012</year>
          , pp.
          <fpage>3679</fpage>
          -
          <lpage>3686</lpage>
          . URL: http://www.lrec-conf.org/proceedings/lrec2012/pdf/1072_Paper.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [28]
          <string-name>
            <surname>J.-C. Kalo</surname>
            , L. Fichtel,
            <given-names>KAMEL</given-names>
          </string-name>
          :
          <article-title>Knowledge Analysis with Multitoken Entities in Language Models</article-title>
          ,
          <source>in: Automated Knowledge Base Construction</source>
          ,
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          [29]
          <string-name>
            <given-names>F.</given-names>
            <surname>Petroni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Piktus</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Fan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Lewis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Yazdani</surname>
          </string-name>
          , N. De Cao,
          <string-name>
            <given-names>J.</given-names>
            <surname>Thorne</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Jernite</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Karpukhin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Maillard</surname>
          </string-name>
          , et al.,
          <article-title>KILT: a Benchmark for Knowledge Intensive Language Tasks</article-title>
          ,
          <source>in: Proceedings of the 2021 Conference of the North American Chapter of the Association for Computational Linguistics: Human Language Technologies</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>2523</fpage>
          -
          <lpage>2544</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          [30]
          <string-name>
            <given-names>J.</given-names>
            <surname>Yu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Tu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Cao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Zhang-Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Lv</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Peng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Yao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Bai</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Xin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Lin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Yun</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Gong</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Qi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Guan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Zeng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Qi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Jin</surname>
          </string-name>
          , J. Liu,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Gu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Yao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Ding</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Hou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Tang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <source>KoLA: Carefully Benchmarking World Knowledge of Large Language Models</source>
          ,
          <year>2023</year>
          . arXiv:
          <volume>2306</volume>
          .
          <fpage>09296</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          [31]
          <string-name>
            <given-names>T.</given-names>
            <surname>Brown</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Mann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Ryder</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Subbiah</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. D.</given-names>
            <surname>Kaplan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Dhariwal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Neelakantan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Shyam</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Sastry</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Askell</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Agarwal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Herbert-Voss</surname>
          </string-name>
          , G. Krueger,
          <string-name>
            <given-names>T.</given-names>
            <surname>Henighan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Child</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Ramesh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Ziegler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Winter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Hesse</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Chen</surname>
          </string-name>
          , E. Sigler,
          <string-name>
            <given-names>M.</given-names>
            <surname>Litwin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Gray</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Chess</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Clark</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Berner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>McCandlish</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Radford</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            <surname>Sutskever</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Amodei</surname>
          </string-name>
          ,
          <article-title>Language Models are Few-Shot Learners</article-title>
          , in: H.
          <string-name>
            <surname>Larochelle</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Ranzato</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Hadsell</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Balcan</surname>
          </string-name>
          , H. Lin (Eds.),
          <source>Advances in Neural Information Processing Systems</source>
          , volume
          <volume>33</volume>
          ,
          <string-name>
            <surname>Curran</surname>
            <given-names>Associates</given-names>
          </string-name>
          , Inc.,
          <year>2020</year>
          , pp.
          <fpage>1877</fpage>
          -
          <lpage>1901</lpage>
          . URL: https://proceedings.neurips.cc/paper_ ifles/paper/2020/file/1457c0d6bfcb4967418bfb8ac142f64a-Paper.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          [32]
          <string-name>
            <given-names>A.</given-names>
            <surname>Piscopo</surname>
          </string-name>
          , E. Simperl,
          <article-title>What we talk about when we talk about wikidata quality: a literature survey</article-title>
          , in: B.
          <string-name>
            <surname>Lundell</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Gamalielsson</surname>
          </string-name>
          , L. Morgan, G. Robles (Eds.),
          <source>Proceedings of the 15th International Symposium on Open Collaboration, OpenSym</source>
          <year>2019</year>
          , Skövde, Sweden,
          <source>August 20-22</source>
          ,
          <year>2019</year>
          , ACM,
          <year>2019</year>
          , pp.
          <volume>17</volume>
          :
          <fpage>1</fpage>
          -
          <lpage>17</lpage>
          :
          <fpage>11</fpage>
          . URL: https://doi.org/10.1145/3306446.3340822. doi:
          <volume>10</volume>
          .1145/3306446.3340822.
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          [33]
          <string-name>
            <given-names>K.</given-names>
            <surname>Shenoy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Ilievski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Garijo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Schwabe</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. A.</given-names>
            <surname>Szekely</surname>
          </string-name>
          ,
          <article-title>A Study of the Quality of Wikidata</article-title>
          ,
          <source>J. Web Semant</source>
          .
          <volume>72</volume>
          (
          <year>2022</year>
          )
          <article-title>100679</article-title>
          . URL: https://doi.org/10.1016/j.websem.
          <year>2021</year>
          .
          <volume>100679</volume>
          . doi:
          <volume>10</volume>
          .1016/j.websem.
          <year>2021</year>
          .
          <volume>100679</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          [34]
          <string-name>
            <given-names>K.</given-names>
            <surname>Alghamdi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Shi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Simperl</surname>
          </string-name>
          , Learning to Recommend Items to Wikidata Editors, in: A.
          <string-name>
            <surname>Hotho</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <string-name>
            <surname>Blomqvist</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Dietze</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Fokoue</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          <string-name>
            <surname>Ding</surname>
            ,
            <given-names>P. M.</given-names>
          </string-name>
          <string-name>
            <surname>Barnaghi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Haller</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Dragoni</surname>
          </string-name>
          , H. Alani (Eds.),
          <source>The Semantic Web - ISWC 2021 - 20th International Semantic Web Conference, ISWC</source>
          <year>2021</year>
          ,
          <string-name>
            <given-names>Virtual</given-names>
            <surname>Event</surname>
          </string-name>
          ,
          <source>October 24-28</source>
          ,
          <year>2021</year>
          , Proceedings, volume
          <volume>12922</volume>
          of Lecture Notes in Computer Science, Springer,
          <year>2021</year>
          , pp.
          <fpage>163</fpage>
          -
          <lpage>181</lpage>
          . URL: https://doi. org/10.1007/978-3-
          <fpage>030</fpage>
          -88361-4_
          <fpage>10</fpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>030</fpage>
          -88361-4\_
          <fpage>10</fpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>