BERT in DeepPavlov¶
BERT (Bidirectional Encoder Representations from Transformers) is a Transformer pre-trained on masked language model and next sentence prediction tasks. This approach showed state-of-the-art results on a wide range of NLP tasks in English.
There are several pre-trained BERT models released by Google Research, more detail about these pretrained models could be found here https://github.com/google-research/bert#pre-trained-models:
BERT-large, English, cased, 24-layer, 1024-hidden, 16-heads, 340M parameters: download from [google]
BERT-base, Chinese, cased, 12-layer, 768-hidden, 12-heads, 110M parameters: download from [google]
We have trained BERT-base model for other languages:
RuBERT, Russian, cased, 12-layer, 768-hidden, 12-heads, 180M parameters: [deeppavlov]
SlavicBERT, Slavic (bg, cs, pl, ru), cased, 12-layer, 768-hidden, 12-heads, 180M parameters: [deeppavlov]
RuBERT was trained on the Russian part of Wikipedia and news data. We used this training data to build vocabulary of Russian subtokens and took multilingual version of BERT-base as initialization for RuBERT 1. SlavicBERT training was done in the same manner as RuBERT.
Here, in DeepPavlov, we made it easy to use pre-trained BERT for downstream tasks like classification, tagging, question answering and ranking. We also provide pre-trained models and examples on how to use BERT with DeepPavlov.
BERT for Classification¶
BertClassifierModel provides easy to use solution for classification problem
using pre-trained BERT. One can use several pre-trained English, multi-lingual and Russian BERT models that are
Two main components of BERT classifier pipeline in DeepPavlov are
Non-processed texts should be given to
bert_preprocessor for tokenization on subtokens,
encoding subtokens with their indices and creating tokens and segment masks.
In case of using one-hot encoded classes in the pipeline, set
bert_classifier has a dense layer of number of classes size upon pooled outputs of Transformer encoder,
it is followed by
softmax activation (
multilabel parameter is set to
true in config).
BERT for Named Entity Recognition (Sequence Tagging)¶
Pre-trained BERT model can be used for sequence tagging. Examples of usage of BERT for sequence tagging can be
found here. The module used for tagging is
To tag each word representations of the first sub-word elements are extracted. So for each word there is only one vector produced.
These representations are passed to a dense layer or Bi-RNN layer to produce distribution over tags. There is
also an optional CRF layer on the top.
Multilingual BERT model allows to perform zero-shot transfer across languages. To use our 19 tags NER for over a hundred languages see Multilingual BERT Zero-Shot Transfer.
BERT for Context Question Answering (SQuAD)¶
Context Question Answering on SQuAD dataset is a task
of looking for an answer on a question in a given context. This task could be formalized as predicting answer start
and end position in a given context.
BertSQuADModel uses two linear
transformations to predict probability that current subtoken is start/end position of an answer. For details check
Context Question Answering documentation page.
BERT for Ranking¶
There are two main approaches in text ranking. The first one is interaction-based which is relatively accurate but
works slow and the second one is representation-based which is less accurate but faster 2.
The interaction-based ranking based on BERT is represented in the DeepPavlov with two main components
and the representation-based ranking with components
BertSepRankerPredictor are for usage in the
where the task for ranking is to retrieve the best possible response from some provided response base with the help of
the trained model. Working examples with the trained models are given here.
Statistics are available here.
Kuratov, Y., Arkhipov, M. (2019). Adaptation of Deep Bidirectional Multilingual Transformers for Russian Language. arXiv preprint arXiv:1905.07213.
McDonald, R., Brokos, G. I., & Androutsopoulos, I. (2018). Deep relevance ranking using enhanced document-query interactions. arXiv preprint arXiv:1809.01682.