      |  entity labels. This is why each model will specify the pipeline to use
      |  in its meta data, as a simple list containing the component names:
  
  +code(false, "json").
      "pipeline": ["tensorizer", "tagger", "parser", "ner"]
  
  p
      |  Although you can mix and match pipeline components, their
      |  #[strong order and combination] is usually important. Some components may
      |  require certain modifications on the #[code Doc] to process it. For
 
</s> remove     |  require certain modifications on the #[code Doc] to process it. For
    |  example, the default pipeline first applies the tensorizer, which
    |  pre-processes the doc and encodes its internal
 </s> add     |  require certain modifications on the #[code Doc] to process it. As the
    |  processing pipeline is applied, spaCy encodes the document's internal </s> remove     | ... the model tells spaCy to use the language #[code "en"] and the pipeline
    |  #[code.u-break ["tensorizer", "tagger", "parser", "ner"]]. spaCy will
    |  then initialise #[code spacy.lang.en.English], and create each pipeline
 </s> add     | ... the model tells spaCy to use the language #[code "en"] and the
    |  pipeline #[code.u-break ["tagger", "parser", "ner"]]. spaCy will then
    |  initialise #[code spacy.lang.en.English], and create each pipeline </s> remove     |  document. This step is similar to the #[+api("tensorizer") #[code Tensorizer]]
    |  component, but the #[code TextCategorizer] uses its own CNN model, to
 </s> add     |  document. The #[code TextCategorizer] uses its own CNN model, to </s> remove     |  As the first component of the
    |  #[+a("/usage/processing-pipelines") processing pipeline], the
    |  tensorizer encodes a document's internal meaning representations as an
 </s> add     |  As the  #[+a("/usage/processing-pipelines") processing pipeline] is
    |  applied spaCy encodes a document's internal meaning representations as an
    "pipeline": ["tagger", "parser", "ner"]
      |  entity labels. This is why each model will specify the pipeline to use
      |  in its meta data, as a simple list containing the component names:
  
  +code(false, "json").
    "pipeline": ["tagger", "parser", "ner"]
  
  p
      |  Although you can mix and match pipeline components, their
      |  #[strong order and combination] is usually important. Some components may
      |  require certain modifications on the #[code Doc] to process it. For
keep keep keep keep replace keep keep keep keep keep
 Don't document the tensorizer for now 
website/usage/_spacy-101/_pipelines.jade