Entity resolution: Discogs masters against MusicBrainz release groups
Three methods score the same blocked candidate pairs and are judged on the same test fold against labelled ground truth. Unlinked MusicBrainz records are unlabelled, not known non-matches: they count toward coverage and unverified accepts, never precision, recall or F1. Every figure here is read from the JSON files the dbt project exports into data/; the page types no number of its own.
Loading the artifact-backed comparison…
Methods on the test fold
| method | pair completeness | precision | recall (labelled) | recall (overall) | F1 | coverage | unverified accepts | review queue | ECE (decisions) |
|---|
Source: fct_eval_metrics.json. Precision, recall and F1 are over labelled A records; coverage counts every test-fold A record; unverified accepts are auto-accepts on unlabelled A records, counted by coverage and not by the accuracy metrics.
Reliability: top-candidate probability against observed correctness
Source: fct_calibration.json, decision level. Point size grows with the bin count.
Review cost against the accept threshold
Source: fct_review_queue.json. Total cost in review-row units at the cost ratio selected: .
What a review budget buys
Source: fct_review_floor.json. Each point is one review floor; the horizontal axis is the queue as a share of the test fold, the vertical axis is recall if every queued row were resolved.
Blocking
| key | pairs | pair completeness |
|---|
Source: fct_blocking.json.
Sources
| source | side | dump | date | licence |
|---|
Source: dim_source.json. Licence texts are in docs/DATA_SOURCES.md of the repository.