ScienceBeam sequence models
Sequence-labelling models for the GROBID-style extraction pipeline used by sciencebeam-parser, trained on GROBID's corpus plus training data generated from open-access preprint and journal corpora.
These are drop-in replacements for individual GROBID models: same feature layout, same
model.wapiti format, and the same labels but one โ GROBID's shipped models also predict
I-<other>, marking the first token of a run of unlabelled text, and these do not. That label is
absent from the models rather than from the corpus, and background text is labelled <other>
throughout instead.
They are selected per model by a parser profile, not as a set, so a profile can take one of these and leave the rest of the pipeline on GROBID's own models.
Artifacts
| path | model | trained on |
|---|---|---|
reference-segmenter/wapiti/2026-09-08_wapiti_grobid_090_scielo_preprints_ore |
reference segmenter | GROBID 0.9.0 corpus + generated scielo_preprints-jats and ore |
citation/wapiti/2026-09-08_wapiti_grobid_090_scielo_preprints_ore |
citation | GROBID 0.9.0 corpus + generated scielo_preprints-jats and ore |
Each directory holds model.wapiti.gz and a training.yml recording what it was trained on, with
which hyperparameters, the feature layout it expects, and the checksum of the file beside it.
Paths are <model>/<engine>/<artifact>, so everything available for one pipeline model is listed
together whichever engine produced it.
The artifact name is the training run: <date>_<engine>_<base>_<training set>. The same name is
used wherever the artifact appears โ a parser config, a benchmark run record, these tables โ so they
refer to each other without a lookup.
Controls
| path | model | trained on |
|---|---|---|
reference-segmenter/wapiti/2026-08-04_wapiti_grobid_090_grobid_only |
reference segmenter | GROBID 0.9.0 corpus alone |
citation/wapiti/2026-08-04_wapiti_grobid_090_grobid_only |
citation | GROBID 0.9.0 corpus alone |
These are GROBID 0.9.0's corpus alone through the same pipeline at the same settings as the models above. They exist so that a difference measured against one of those is attributable to the added training data rather than to the pipeline. They are not recommended for serving: GROBID's own published models are trained on that corpus and are the ones to use.
Use
In a sciencebeam-parser config, as a sequence_model_profiles entry:
sequence_model_profiles:
wapiti_scielo_preprints_ore:
extends: grobid_crf_0_9_0
reference_segmenter:
path: 'https://huggingface.co/elifepathways/sciencebeam-sequence-models/resolve/<commit-sha>/reference-segmenter/wapiti/2026-09-08_wapiti_grobid_090_scielo_preprints_ore'
engine: 'wapiti'
citation:
path: 'https://huggingface.co/elifepathways/sciencebeam-sequence-models/resolve/<commit-sha>/citation/wapiti/2026-09-08_wapiti_grobid_090_scielo_preprints_ore'
engine: 'wapiti'
The path is a directory; the parser appends model.wapiti.gz.
Pin a commit sha rather than main, so a change to what a config serves is a visible diff. A
HEAD request against any resolve/main URL here returns the current one as X-Repo-Commit.
These models were selected against GROBID 0.9.0 on an internal benchmark of open-access corpora. How much they help depends on the corpus and on what is being scored, so it is worth measuring on your own documents rather than taking a number from ours.
Training data
Two kinds of input, listed per model in training.yml:
- GROBID 0.9.0's own training data for that model โ the only input the
0.9.0version applies to, and the source of the feature layout, label set and CRF template the models share. - Training data generated by
sciencebeam-parserfrom the PDF and JATS of open-access articles, from two corpora:- SciELO Preprints (DOI prefix
10.1590), CC-BY 4.0 as recorded per article; - Open Research Europe (DOI prefix
10.12688), which publishes under CC-BY 4.0 as platform policy.
- SciELO Preprints (DOI prefix
The generated training data is not published, and neither is the collection of source articles it
was generated from: both are derived from those corpora and redistribution is governed by their
terms. So training.yml identifies each generated input by the path it was written to rather than
by a name that resolves. Retraining from scratch needs that generation step rerunning rather than a
download; training.yml records the inputs and hyperparameters it would need.
Attribution
Derived from GROBID (Apache-2.0) โ its model architecture, feature layout, label sets, CRF templates and training corpus โ with additional training data generated from the CC-BY 4.0 articles of SciELO Preprints and Open Research Europe, as named above. Modified in that the models are retrained on that combined corpus; they are not GROBID's published models and are not endorsed by the GROBID project.