<!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>Aggregation-Based Answering for Broad Product Questions</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Eilon Sheetrit</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Yuval Nezri</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Avihai Mejer</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>David Carmel</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Reichman University</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>Product Question Answering (PQA) is a popular and important feature in e-commerce services that many customers use as part of their shopping journey. Most previous works on PQA focus on questions that were asked in the context of a specific product. In this work we address a diferent use case of answering product questions without the context of a specific product. We refer to these questions as Broad Product Questions (BPQ) as these questions often target a broad set of relevant products, such as “Do jeans shrink after a wash?”. We propose a new answering approach to address BPQs by aggregating information from a set of relevant products. We highlight the advantages of the aggregation-based answering approach in context of e-commerce, and we present an empirical evaluation of the utility users find in these answers compared to common web retrieval-based answers.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;question answering</kwd>
        <kwd>broad product questions</kwd>
        <kwd>aggregation-based answers</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Product Question Answering (PQA) is an important and helpful feature in e-commerce services
that many customers use as part of their shopping journey [
        <xref ref-type="bibr" rid="ref1 ref2 ref3">1, 2, 3</xref>
        ]. The common use case for
PQA are questions which are asked in the context of a specific product, for example, via a Q&amp;A
search bar on the product’s details page. A reference to the specific product can be explicit, e.g.
“how should I clean this humidifier ?”, or implied, such as “Can I turn of the display?” , asked
in the context of a specific humidifier item. Most of the existing answering strategies utilize
semi-structured information provided on the product details page, namely product description
and specifications (e.g., [
        <xref ref-type="bibr" rid="ref4 ref5 ref6 ref7">4, 5, 6, 7</xref>
        ]), community Q&amp;As (e.g., [
        <xref ref-type="bibr" rid="ref1 ref8 ref9">1, 8, 9</xref>
        ]), and customer reviews (e.g.,
[
        <xref ref-type="bibr" rid="ref1 ref10 ref11 ref12 ref13 ref14">1, 10, 11, 12, 13, 14</xref>
        ]).
      </p>
      <p>
        In this work we address a diferent use case of answering product questions that are not
associated with a specific product, but rather address a broad set of relevant products, for
example, “how many watts an air conditioner takes?” ; we refer to these questions as Broad
Product Questions (BPQs). Such questions are issued by customers on the search bar of
ecommerce websites without the context of a specific product. These questions are commonly
answered using a Web-Based Question Answering (Web-QA) approach [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], i.e., retrieving an
answer based on relevant text snippets from the web.
      </p>
      <p>While Web-QA has made much progress in recent years, it sufers from several limitations in
answering product related questions. Due to the highly dynamic nature of product information
(new versions, price changes) Web-based answers are not guaranteed to be up-to-date, and, in
the context of an e-commerce service, to be grounded in active products, i.e. products that are
still available and can be purchased. Another notable limitation is the lack of ability to answer a
question at varying specificity levels. Several examples are shown in Table 1, where commercial
search engines, who had recently expanded their question answering capabilities, retrieve a
good answer to a broad product question, e.g., “how heavy is a pillow”, however when adding a
qualifier to the question, such as “how heavy is a feather pillow”, the engines fail to provide a
satisfying answer. In other cases, the web-based answer relates to only one specific product,
rather than to the family of products that the question asks about (See the “Toshiba microwave”
example in Table 1).</p>
      <p>In this work we propose a novel answering framework for addressing BPQs, in the context of
an e-commerce service, which allows mitigating the aforementioned limitations. The answering
framework, illustrated in Figure 1, is based on aggregation of information from a set of relevant
products and operates as follows: (1) the target item-name which represents the requested
product set is identified in the question, (2) a representative set of relevant products are gathered,
(3) the relevant information is extracted for each product in the set, and (4) an answer is generated
from the aggregated information. Since the answer is algorithmically generated from the
ecommerce catalog, the freshness and quality of the data is grounded, the set broadness of
relevant products is under control, and the answer is associated only with concrete products
that are currently available for purchase, while omitting ‘ghost’ products which have vanished
from the market. Moreover, it is possible to refer to several concrete relevant products directly
in the answer. For example, the question “how heavy are thermal curtains?” is answered by
our method with “Between 1.2 and 5.1 pounds, based on 42 thermal curtains products. Several
alternatives include H.VERSAILTEX (1.9 lb), Deconovo (2.9 lb), and NICETOWN (5 lb).”. We refer to
these type of answers as Aggregation-based Answers. Several more PQA examples are presented
in Table 2. The empirical study we present suggests that such answers can complement, and in
some cases replace, the web-based answers.</p>
      <p>The aggregation-based answering approach can gather product information from a variety of
sources such as product-description, specifications, Q&amp;As, and customer reviews. However, as
a first step, we focus in this work on product specifications only and limit ourselves to product
attribute questions. We leave for future work the utilization of additional sources for BPQ
answering, and the handling of additional question types. In the rest of the paper we (i) describe
in detail the BPQ answering framework, (ii) present empirical evaluation of the utility that users
ifnd in aggregation-based answers. We also report on user satisfaction results from an online
experiment of presenting the new form of answers to customers of an e-commerce service.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <p>
        The line of work mostly related to ours is on answering product-related questions; e.g., [
        <xref ref-type="bibr" rid="ref1 ref14 ref16 ref2 ref3 ref4 ref7 ref8">2,
16, 3, 14, 1, 8, 4, 7</xref>
        ]. The retrieved answer can be extracted from the product related Q&amp;As
[
        <xref ref-type="bibr" rid="ref1 ref2 ref3 ref4 ref8 ref9">4, 1, 2, 3, 8, 9</xref>
        ], from customer reviews [
        <xref ref-type="bibr" rid="ref1 ref12 ref13 ref14 ref16 ref17 ref3 ref4">13, 12, 4, 1, 16, 17, 14, 3</xref>
        ], or by aggregating multiple
sources of information [
        <xref ref-type="bibr" rid="ref10 ref11 ref18">18, 10, 11</xref>
        ]. For a comprehensive survey on PQA approaches we refer
the reader to the work of Deng et al. [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ]. All these works focus on questions asked in the
context of a specific product.
      </p>
      <p>
        Answering attribute questions is a sub-task of Question Answering [
        <xref ref-type="bibr" rid="ref15 ref20 ref7">15, 20, 7</xref>
        ], and is also
closely related to the task of attribute value extraction [
        <xref ref-type="bibr" rid="ref21 ref22 ref23">21, 22, 23</xref>
        ]. Previous works focused
on retrieving a single table entry or aggregating some entry values that correctly answer the
question [
        <xref ref-type="bibr" rid="ref23 ref24 ref25 ref26 ref27">24, 23, 25, 26, 27</xref>
        ]. However, these works assume the table of data exists, while in our
work we dynamically collect the relevant data. These methods can handle complex questions
that require the consideration of table entry relations and the whole table structure. Integrating
inter-relations within attribute values into our method is an interesting direction for future
research.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Aggregation Based Answering Framework</title>
      <p>The following section describes the aggregation-based framework for answering BPQs. We
focus on answering attribute questions from product specifications (BPQ-PS). Figure 1 describes
the BPQ-PS framework, its components are further discussed below.</p>
      <p>Q: How heavy
are thermal
curtains?
Item-Name</p>
      <p>Extraction
[thermal curtains]</p>
      <p>Construction of a
Representative
Product Set
…</p>
      <p>…
Attribute
Length
Material
Weight
Brand</p>
      <p>Value
75 inch
Linen
2 pounds
Deconovo</p>
      <p>Answer</p>
      <p>Generation
A: Between 1.2 and 5.1</p>
      <p>pounds</p>
      <p>Based on 42 popular
thermal curtain products.</p>
      <sec id="sec-3-1">
        <title>3.1. Item-Name Extraction</title>
        <p>First, an item-name is extracted from the user’s question. An item-name refers to the phrase
in the question specifying the product or product-set the user asks about. This item-name is
then used to infer the product set for aggregation, therefore, it is crucial that it will be specific
as possible, capturing all available information in the query. For example, for the question:
“How heavy are thermal curtains?”, if only the item “curtains" is identified, while the “thermal”
attribute is omitted, the accumulation will be applied to regular curtains, resulting with a wrong
answer.</p>
        <p>
          Item-names can be identified by Named Entity Recognition (NER) which is a well known
task that has been studied intensively by the NLP community (e.g. [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ]), and many publicly
available tools exist for this task [
          <xref ref-type="bibr" rid="ref29 ref30">29, 30</xref>
          ]. In our BPQ-PS implementation, we use an in-house
Transformers-based NER tool [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ] that was specifically trained for identifying item-names in
product related queries and questions.
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Representative Product Set Extraction</title>
        <p>Next, we collect a representative set of products that are relevant to the extracted item-name.
When choosing the representative product set multiple aspects should be considered, such as
freshness, availability, popularity, diversity, and completeness. In our BPQ-PS implementation
we focus on popular products, rather than on a complete set, as these better represent the
products that a typical user is looking for. We leverage the e-commerce product search service
to retrieve a large and diverse collection of products relevant to the extracted item-name. These
products are also guaranteed to be up-to-date and available for immediate purchase.</p>
        <p>Popular items from the retrieved collection are then selected by leveraging historical
purchasing data of several months; only products that were purchased more than a certain fraction
of times, following a product search with the item-name as the query, are retained. As a result,
the representative product set contains only up-to-date, available, popular, and most relevant
products to the item-name.</p>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. Data Acquisition</title>
        <p>In the data acquisition stage we extract the product-centric data that is relevant to the user’s
question, for each product in the product set. We focus on product attribute questions that
can be answered by product specifications. Product specifications is a collection of (attribute:
value) pairs representing the product, typically a few dozens per product. Attribute values may
be Boolean (e.g. (dishwasher-safe: true)), numeric, typically accompanied with their units, (e.g.
(display size: 5.1 inches)), or categorical (e.g. (connectivity: 5G, 4G, Bluetooth)). Some attributes
are repeated for most products across all categories, e.g., brand and weight, while others are
unique to some categories or to a subset of products, such as calories and wireless connectivity.</p>
        <p>
          The attribute value extraction step requires identifying the relevant attribute to answer the
user’s question. For the question “How heavy are thermal curtains?” the relevant attribute
weight should be identified. To this end, we follow the template method proposed in previous
work [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. For each (attribute: value) pair we generate a template-based answer in the form “The
attribute is value” (e.g. “The weight is 32 kg”) and estimate the probability that this answer
satisfies the user’s question. We then select the attribute with the highest probability which is
above a pre-defined threshold; no answer is returned if no such attribute exists. The probability
that an answer satisfies the question is estimated using a pre-trained RoBERTa model [
          <xref ref-type="bibr" rid="ref32">32</xref>
          ],
ifne-tuned on Amazon-PQA corpus [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] 1.
        </p>
        <p>In the common PQA use-case, where the goal is providing relevant information for a single
product, returning an answer based on one extracted (attribute:value) pair might be suficient.
In our case, however, aggregation is required over many pairs, and in general, the attribute
information associated with diferent products is provided by diferent manufacturers and sellers.
Therefore, additional steps of data cleansing is required, including normalization, unification,
and filtering. For Boolean attributes, we transform each value to Boolean and count the portion
of products with a positive value (’true’) and negative value (’false’). For numeric attributes, we
apply an open source unit normalization library2 and inter quartile range outlier filtering, to
enable measuring the range of values and other statistics. For categorical attributes we filter
out outliers, typos and invalid values using manually generated regular expressions.</p>
      </sec>
      <sec id="sec-3-4">
        <title>3.4. Answer Generation</title>
        <p>Recent advancement in language generation methods allow transforming the data elements
collected in the previous stage into a natural language answer. However, in order to focus our
analysis on the utility of the aggregated answers, rather than on the language quality, we choose
to utilize a handful of manually-curated textual templates for answer generation. The answer
template provides details on the number of relevant products it is based on, and the value
aggregation over this set. For categorical attributes (e.g. colors or materials) we provide up to
ifve most frequent attribute values. For numeric attributes (e.g. weight or wattage) we provide
the range of values. For Boolean attributes (e.g. microwave safe), we provide the ratio between
positive and negative attribute values, or a yes/no answer in case of agreement. Examples for
each type of answer template are presented in Table 2.</p>
        <sec id="sec-3-4-1">
          <title>1We follow the fine-tuning process described in Shen et al. [7]. 2https://github.com/hgrecco/pint</title>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Experiments</title>
      <p>The main objective of our experiments is to evaluate the utility users find in
aggregationbased answers and the merits of using these answers to augment web-based answers. For that,
we asked human annotators to evaluate the quality of Web-QA and BPQ-PS answers, and a
combination of the two. We also conducted an online experiment on a commercial e-commerce
service and report on users’ satisfaction.</p>
      <p>
        Question Data. Our experiments were conducted on a subset of the Natural Questions (NQ)
dataset [
        <xref ref-type="bibr" rid="ref33">33</xref>
        ]. We applied an in house NER classifier [
        <xref ref-type="bibr" rid="ref31">31</xref>
        ] to detect the subset of product questions;
i.e., questions that refer to a product. In total we were able to identify 7, 583 product questions.
We refer to this subset as PNQ.
      </p>
      <p>BPQ-PS. While running BPQ-PS to answer the questions in PNQ, we applied several filters in
order to identify questions to which the answering method is suitable. First, we retained only
questions for which a single item-name was identified. Questions with zero item-names are
obviously not suitable, and questions with multiple item-names pose challenges in constructing
a representative product set that we defer to future work. As our focus is on broad questions,
we retained only questions that had at least 5 valid attribute values, from diferent products,
following the product set extraction and attribute-value extraction steps. This process resulted in
429 questions that can be answered by BPQ-PS, reflecting coverage of 5.7% of the PNQ dataset 3.
Leveraging additional data sources beyond product specifications, e.g. customer reviews or
product descriptions, can increase the coverage of the aggregation-based approach and is left
for future work.</p>
      <p>
        Web-QA. We run a Web-QA system to retrieve web-based answers for all the 429 questions
that were answered by BPQ-PS. The Web-QA system we used is of a commercial e-commerce
service; it indexes web pages from a broad and diverse set of websites and retrieves the most
relevant answer using a combination of dense passage retrieval [
        <xref ref-type="bibr" rid="ref34">34</xref>
        ] and answer selection [
        <xref ref-type="bibr" rid="ref35">35</xref>
        ]
algorithm.
3The subset of questions we retained does not represent a uniform sample of the question trafic submitted on
e-commerce platforms.
      </p>
      <sec id="sec-4-1">
        <title>4.1. Results</title>
        <p>Manual Quality Evaluation. The answers for the 429 questions, both from Web-QA and
BPQ-PS, were evaluated each by 3 human annotators4. The annotators were asked to judge
each answer independently as either: relevant, somewhat relevant, or not-relevant, the labels
were determined by a majority vote. Among the BPQ-PS answers, 46% were labeled as relevant,
22% as somewhat relevant, and the remaining 32% as not-relevant. The main reason for labeling
an answer as not-relevant, accounting for 72% of these cases, was that the question is not
an attribute question. Additional reasons for non-relevance are wrong attribute selection or
incorrect item-name extraction from the question, these account for 12% and 7% of the
notrelevant cases, respectively. The Web-QA answers were labeled as relevant and somewhat
relevant for 84% and 8% of the cases respectively, attesting to the high quality and maturity of
the Web-QA system we used.</p>
        <p>In order to assess the utility users can find in augmenting the high quality Web-QA answers
with BPQ-PS answers we conducted a second study. We evaluated 169 questions to which
both the BPQ-PS and Web-QA answers were annotated as relevant. First, each pair of answers
was reviewed by 3 annotators in order to characterize the relationship between them. Among
the 169 pairs the distribution over relationship type was: contradiction (47%), inclusion (21%),
complementary (19%), equivalence (5%), and other (8%). Next, annotators where asked to
evaluate the original Web-QA answer and an enriched Web-QA+BPQ-PS answer5, for example,
for the questions “What is the American flag made out of?” , the enriched answer is “According
to snippets.com: The American flag is made out of polyester materials. In addition: based on
87 popular American flag products, there are 6 materials: nylon, polyester, polypropylene, spun
polyester, polyurethane, and cotton.”. The annotators were asked to score each answer from 1
to 5 to indicate how relevant, complete and helpful an answer is. The annotation results are
shown in Table 3. We see that on average, the Web-QA answers received very high score of 4.7,
and yet, enriching them with BPQ-PS answers further improves the scores to 4.73. In particular
we find a statistically significant increase of +0.17 when the answers complement each other,
yet when the answers contradict or contain each other the scores are on par.
Online Experiment. In addition to the manual crowd-based evaluation, we evaluate the
satisfaction of e-commerce users from the aggregation-based answers in an online experiment.
On a commercial e-commerce search bar users typically submit short queries seeking for</p>
        <sec id="sec-4-1-1">
          <title>4We used MTurk crowdsourcing platform: https://www.mturk.com/ 5Diferent annotators judged the two flavors of the answers, it was not a side-by-side comparison</title>
          <p>products. Additionally, as shown in Fig 2, users can submit full natural language questions
and receive a direct answer in addition to the standard search results. In order to focus on
user satisfaction from the new form of answers, rather than on answer quality, we validated
ofline the relevance of the answers before serving them to users. Specifically, in an ofline
process, we collected a sample of popular questions on the service, and answered them with
BPQ-PS. We then manually validated the answers and retained only the relevant ones. This
PQ&amp;A bank is then used to serve online newly submitted questions that are highly similar to
one of the questions in our bank. Figure 2 presents the direct answer to the question, for which
users were asked to provide feedback. We measure the Positive Response Rate (PRR), i.e., the
percentage of times users selected “Yes”. The PRR for BPQ-PS yield relative improvement of
∼ 34% compared to the PRR for the Web-QA. While part of the high PRR may be attributed to
the manual validation of the BPQ-PS bank, we nevertheless believe it shows that users find the
new form of answers engaging and helpful.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusions and Future Work</title>
      <p>In this work we addressed the task of answering BPQs, i.e., questions that refer to a broad set of
products which are asked outside the context of a specific product. We described an
aggregationbased answering approach, and implemented BPQ-PS which utilizes product specification data
to address attribute questions. Our empirical evaluation demonstrates the merits and utility of
the new form of answers. In future work we plan to extend the aggregation-based answering
approach by leveraging additional information sources such as community Q&amp;As and customer
reviews.</p>
      <p>
        Another interesting direction is leveraging recent large language models to produce
highquality fluent answers. With retrieval augmented generation (RAG) techniques [
        <xref ref-type="bibr" rid="ref36">36</xref>
        ], the answer
generator is exposed to pieces of evidence based on information retrieved from external
resources, leading to more grounded, accurate, and up-to-date answer. For example, the answer
of ChatGPT [
        <xref ref-type="bibr" rid="ref37">37</xref>
        ] for the question “how many watts does a car cigarette lighter produce?” is “A
car cigarette lighter typically produces up to 120 watts of power (12 volts x 10 amps).” However,
when enriching the prompt with the category-based information “In an e-commerce website we
found the following Wattage values for car cigarette lighter: [
        <xref ref-type="bibr" rid="ref10 ref15 ref24 ref30">10, 15, 24, 30, 38, 80, 100, 120, 150,180,
200</xref>
        ] watts” ; ChatGPT enriched its answer to: “The wattage values for car cigarette lighters listed
on the provided e-commerce website range from 10 watts to 200 watts. However, the typical power
output of a car cigarette lighter is up to 120 watts.”. Retrieval augmented generation opens an
interesting direction for improving broad product question answering which we leave for future
research.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>D.</given-names>
            <surname>Carmel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Lewin-Eytan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Maarek</surname>
          </string-name>
          ,
          <article-title>Product question answering using customer generated content-research challenges</article-title>
          ,
          <source>in: Proc. of SIGIR</source>
          ,
          <year>2018</year>
          , pp.
          <fpage>1349</fpage>
          -
          <lpage>1350</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>S.</given-names>
            <surname>Gao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Ren</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Zhao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Zhao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Yin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Yan</surname>
          </string-name>
          ,
          <article-title>Product-aware answer generation in e-commerce question-answering</article-title>
          ,
          <source>in: Proc. of WSDM</source>
          ,
          <year>2019</year>
          , pp.
          <fpage>429</fpage>
          -
          <lpage>437</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>A.</given-names>
            <surname>Kulkarni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Mehta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Garg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Bansal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Rasiwasia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Sengamedu</surname>
          </string-name>
          ,
          <article-title>Productqna: Answering user questions on e-commerce product pages</article-title>
          ,
          <source>in: Proc. of WWW</source>
          ,
          <year>2019</year>
          , pp.
          <fpage>354</fpage>
          -
          <lpage>360</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>L.</given-names>
            <surname>Cui</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Huang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Wei</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Tan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Duan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Zhou</surname>
          </string-name>
          ,
          <article-title>Superagent: A customer service chatbot for e-commerce websites</article-title>
          ,
          <source>in: Proc. of ACL</source>
          ,
          <year>2017</year>
          , pp.
          <fpage>97</fpage>
          -
          <lpage>102</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>T.</given-names>
            <surname>Lai</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Bui</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Lipka</surname>
          </string-name>
          ,
          <article-title>A simple end-to-end question answering model for product information</article-title>
          ,
          <source>in: Proc. of ECONLP</source>
          ,
          <year>2018</year>
          , pp.
          <fpage>38</fpage>
          -
          <lpage>43</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>T. M.</given-names>
            <surname>Lai</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Bui</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Lipka</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <article-title>Supervised transfer learning for product information question answering</article-title>
          ,
          <source>in: Proc. of ICMLA</source>
          , IEEE,
          <year>2018</year>
          , pp.
          <fpage>1109</fpage>
          -
          <lpage>1114</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>X.</given-names>
            <surname>Shen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Barlacchi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Del Tredici</surname>
          </string-name>
          , W. Cheng, A. de Gispert,
          <article-title>semipqa: A study on product question answering over semi-structured data</article-title>
          ,
          <source>in: Proc. of ECNLP</source>
          ,
          <year>2022</year>
          , pp.
          <fpage>111</fpage>
          -
          <lpage>120</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>O.</given-names>
            <surname>Rozen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Carmel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Mejer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Mirkis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Ziser</surname>
          </string-name>
          ,
          <article-title>Answering product-questions by utilizing questions from other contextually similar products</article-title>
          ,
          <source>in: Proc. of NAACL</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>242</fpage>
          -
          <lpage>253</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>H.</given-names>
            <surname>Mittal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Chakrabarti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Bayar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. A.</given-names>
            <surname>Sharma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Rasiwasia</surname>
          </string-name>
          ,
          <article-title>Distantly supervised transformers for e-commerce product qa</article-title>
          ,
          <source>in: Proc. of NAACL</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>4008</fpage>
          -
          <lpage>4017</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Feng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Ren</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Zhao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Sun</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Li</surname>
          </string-name>
          <article-title>, Multi-type textual reasoning for product-aware answer generation</article-title>
          ,
          <source>in: Proc. of SIGIR</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>1135</fpage>
          -
          <lpage>1145</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>S.</given-names>
            <surname>Gao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Ren</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Zhao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Yan</surname>
          </string-name>
          ,
          <article-title>Meaningful answer generation of e-commerce question-answering</article-title>
          ,
          <source>TOIS</source>
          <volume>39</volume>
          (
          <year>2021</year>
          )
          <fpage>1</fpage>
          -
          <lpage>26</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>J. McAuley</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Yang</surname>
          </string-name>
          ,
          <article-title>Addressing complex and subjective product-related queries with customer reviews</article-title>
          ,
          <source>in: Proc. of WWW</source>
          ,
          <year>2016</year>
          , pp.
          <fpage>625</fpage>
          -
          <lpage>635</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>M.</given-names>
            <surname>Wan</surname>
          </string-name>
          ,
          <string-name>
            <surname>J. McAuley</surname>
          </string-name>
          ,
          <article-title>Modeling ambiguity, subjectivity, and diverging viewpoints in opinion question answering systems</article-title>
          ,
          <source>in: Proc. of ICDM)</source>
          , IEEE,
          <year>2016</year>
          , pp.
          <fpage>489</fpage>
          -
          <lpage>498</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>S.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. H.</given-names>
            <surname>Lau</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Chan</surname>
          </string-name>
          , C. Paris,
          <article-title>Discovering relevant reviews for answering product-related queries</article-title>
          ,
          <source>in: Proc. of ICDM</source>
          ,
          <year>2019</year>
          , pp.
          <fpage>1468</fpage>
          -
          <lpage>1473</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>D.</given-names>
            <surname>Azari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Horvitz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. T.</given-names>
            <surname>Dumais</surname>
          </string-name>
          , E. Brill,
          <article-title>Web-based question answering: A decisionmaking perspective</article-title>
          ,
          <source>CoRR abs/1212</source>
          .2453 (
          <year>2012</year>
          ). URL: http://arxiv.org/abs/1212.2453. arXiv:
          <volume>1212</volume>
          .
          <fpage>2453</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>S.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Ji</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Zhou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <article-title>Driven answer generation for product-related questions in e-commerce</article-title>
          ,
          <source>in: Proc. of WSDM</source>
          ,
          <year>2019</year>
          , pp.
          <fpage>411</fpage>
          -
          <lpage>419</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>J.</given-names>
            <surname>Zhao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Guan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Sun</surname>
          </string-name>
          , Riker:
          <article-title>Mining rich keyword representations for interpretable product question answering</article-title>
          ,
          <source>in: Proc. of</source>
          ,
          <year>2019</year>
          , pp.
          <fpage>1389</fpage>
          -
          <lpage>1398</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>W.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Q.</given-names>
            <surname>Yu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Lam</surname>
          </string-name>
          ,
          <article-title>Answering product-related questions with heterogeneous information</article-title>
          ,
          <source>in: Proc. of AACL</source>
          ,
          <year>2020</year>
          , pp.
          <fpage>696</fpage>
          -
          <lpage>705</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Deng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Q.</given-names>
            <surname>Yu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Lam</surname>
          </string-name>
          ,
          <article-title>Product question answering in e-commerce: A survey</article-title>
          ,
          <year>2023</year>
          . URL: https://arxiv.org/abs/2302.08092. doi:
          <volume>10</volume>
          .48550/ARXIV.2302.08092.
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <surname>M. A. C. Soares</surname>
            ,
            <given-names>F. S.</given-names>
          </string-name>
          <string-name>
            <surname>Parreiras</surname>
          </string-name>
          ,
          <article-title>A literature review on question answering techniques, paradigms and systems</article-title>
          ,
          <source>Journal of King Saud University-Computer and Information Sciences</source>
          <volume>32</volume>
          (
          <year>2020</year>
          )
          <fpage>635</fpage>
          -
          <lpage>646</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>D.</given-names>
            <surname>Davidov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Rappoport</surname>
          </string-name>
          ,
          <article-title>Extraction and approximation of numerical attributes from the web</article-title>
          ,
          <source>in: Proc. of ACL</source>
          ,
          <year>2010</year>
          , pp.
          <fpage>1308</fpage>
          -
          <lpage>1317</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Song</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Cai</surname>
          </string-name>
          ,
          <article-title>A put-based approach to automatically extracting quantities and generating final answers for numerical attributes</article-title>
          ,
          <source>Entropy</source>
          <volume>18</volume>
          (
          <year>2016</year>
          )
          <fpage>235</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>H.</given-names>
            <surname>Sun</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Ma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>He</surname>
          </string-name>
          , W.-t. Yih,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Su</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Yan</surname>
          </string-name>
          ,
          <article-title>Table cell search for question answering</article-title>
          ,
          <source>in: Proc of. WWW</source>
          ,
          <year>2016</year>
          , pp.
          <fpage>771</fpage>
          -
          <lpage>782</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>P.</given-names>
            <surname>Pasupat</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Liang</surname>
          </string-name>
          ,
          <article-title>Compositional semantic parsing on semi-structured tables</article-title>
          ,
          <source>in: Proc. of ACL</source>
          ,
          <year>2015</year>
          , pp.
          <fpage>1470</fpage>
          -
          <lpage>1480</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>J.</given-names>
            <surname>Herzig</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. K.</given-names>
            <surname>Nowak</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Mueller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Piccinno</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Eisenschlos</surname>
          </string-name>
          , Tapas:
          <article-title>Weakly supervised table parsing via pre-training</article-title>
          ,
          <source>in: Proc. of ACL</source>
          ,
          <year>2020</year>
          , pp.
          <fpage>4320</fpage>
          -
          <lpage>4333</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <given-names>P.</given-names>
            <surname>Yin</surname>
          </string-name>
          , G. Neubig, W.-t. Yih,
          <string-name>
            <given-names>S.</given-names>
            <surname>Riedel</surname>
          </string-name>
          ,
          <article-title>Tabert: Pretraining for joint understanding of textual and tabular data</article-title>
          ,
          <source>in: Proc. of ACL</source>
          ,
          <year>2020</year>
          , pp.
          <fpage>8413</fpage>
          -
          <lpage>8426</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [27]
          <string-name>
            <given-names>K.</given-names>
            <surname>Chakrabarti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Shakeri</surname>
          </string-name>
          , G. Cao,
          <article-title>Open domain question answering using web tables</article-title>
          , arXiv preprint arXiv:
          <year>2001</year>
          .
          <volume>03272</volume>
          (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [28]
          <string-name>
            <given-names>A.</given-names>
            <surname>Mikheev</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Moens</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Grover</surname>
          </string-name>
          ,
          <article-title>Named entity recognition without gazetteers</article-title>
          ,
          <source>in: Ninth Conference of the European Chapter of the Association for Computational Linguistics</source>
          ,
          <year>1999</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>8</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          [29]
          <string-name>
            <given-names>M.</given-names>
            <surname>Honnibal</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Montani</surname>
          </string-name>
          , spaCy 2:
          <article-title>Natural language understanding with Bloom embeddings, convolutional neural networks and incremental parsing</article-title>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          [30]
          <string-name>
            <given-names>S.</given-names>
            <surname>Bird</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Klein</surname>
          </string-name>
          , E. Loper,
          <article-title>Natural language processing with Python: analyzing text with the natural language toolkit, "</article-title>
          <string-name>
            <surname>O'Reilly Media</surname>
          </string-name>
          ,
          <source>Inc."</source>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          [31]
          <string-name>
            <given-names>B.</given-names>
            <surname>Fetahu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Fang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Rokhlenko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Malmasi</surname>
          </string-name>
          ,
          <article-title>Gazetteer enhanced named entity recognition for code-mixed web queries</article-title>
          ,
          <source>in: Proceedings of the 44th International ACM SIGIR Conference on Research and Development in Information Retrieval</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>1677</fpage>
          -
          <lpage>1681</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          [32]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Ott</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Goyal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Du</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Joshi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Levy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lewis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Zettlemoyer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Stoyanov</surname>
          </string-name>
          ,
          <article-title>Roberta: A robustly optimized bert pretraining approach</article-title>
          , arXiv preprint arXiv:
          <year>1907</year>
          .
          <volume>11692</volume>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          [33]
          <string-name>
            <given-names>T.</given-names>
            <surname>Kwiatkowski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Palomaki</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Redfield</surname>
          </string-name>
          , M. Collins,
          <string-name>
            <given-names>A.</given-names>
            <surname>Parikh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Alberti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Epstein</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Polosukhin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Devlin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Lee</surname>
          </string-name>
          , et al.,
          <article-title>Natural questions: a benchmark for question answering research</article-title>
          , TACL
          <volume>7</volume>
          (
          <year>2019</year>
          )
          <fpage>453</fpage>
          -
          <lpage>466</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          [34]
          <string-name>
            <given-names>V.</given-names>
            <surname>Karpukhin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Oguz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Min</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Lewis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Edunov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Chen</surname>
          </string-name>
          , W.-t. Yih,
          <article-title>Dense passage retrieval for open-domain question answering</article-title>
          ,
          <source>in: Proceedings of the 2020 Conference on Empirical Methods in Natural Language Processing (EMNLP)</source>
          ,
          <year>2020</year>
          , pp.
          <fpage>6769</fpage>
          -
          <lpage>6781</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref35">
        <mixed-citation>
          [35]
          <string-name>
            <given-names>S.</given-names>
            <surname>Garg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Vu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Moschitti</surname>
          </string-name>
          ,
          <article-title>Tanda: Transfer and adapt pre-trained transformer models for answer sentence selection</article-title>
          ,
          <source>in: Proceedings of the AAAI conference on artificial intelligence</source>
          , volume
          <volume>34</volume>
          ,
          <year>2020</year>
          , pp.
          <fpage>7780</fpage>
          -
          <lpage>7788</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref36">
        <mixed-citation>
          [36]
          <string-name>
            <given-names>P.</given-names>
            <surname>Lewis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Perez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Piktus</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Petroni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Karpukhin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Goyal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Küttler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lewis</surname>
          </string-name>
          , W.-t. Yih,
          <string-name>
            <given-names>T.</given-names>
            <surname>Rocktäschel</surname>
          </string-name>
          , et al.,
          <article-title>Retrieval-augmented generation for knowledge-intensive nlp tasks</article-title>
          ,
          <source>Advances in Neural Information Processing Systems</source>
          <volume>33</volume>
          (
          <year>2020</year>
          )
          <fpage>9459</fpage>
          -
          <lpage>9474</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref37">
        <mixed-citation>
          [37]
          <string-name>
            <surname>OpenAI</surname>
          </string-name>
          , Chatgpt,
          <year>2022</year>
          . URL: https://openai.com/blog/chatgpt.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>