feat(pelagios): tune Pleiades matcher against the live corpus#75
Merged
Conversation
Ran propose_pleiades_links over all 838 distinct findspots (5,932
inscriptions) pulled from the live API. Findings, now folded in:
- Stem-prefix index in propose_links (prefix_len, default 3). A full
difflib pass over the ~11k-place gazetteer does not finish; the indexed
path runs in ~2s. prefix_len=0 forces the old full comparison.
- Stopwords: add `cum`/`et` and museum/collection scaffolding (museo,
publico, collezione, …). Recovers ~70 inscriptions that scored just under
threshold ("Clusium cum agro", "Clusii in museo publico" → Clusium 1.0).
- Default threshold 0.84 → 0.90. Sweep showed sub-0.90 recall is mostly
wrong (Clusino GA.→lake Clusinus, Parisiis→Parsiana, "in fronte DA.").
At 0.90: 75 findspots / 1,280 inscriptions (58%); exact-stem alone covers
53%. docs/PELAGIOS.md records the sweep + the open precision gaps
(place-type disambiguation, non-findspot string filtering).
- Tests: cum phrase, museum scaffolding, prefix-index vs full-scan agreement.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to the Pelagios place axis: ran
propose_pleiades_linksover all 838 distinct findspots / 5,932 inscriptions pulled from the live API and tuned the matcher.Changes
propose_links(prefix_len, default 3). A fulldifflibpass over the ~11k-place gazetteer doesn't finish; indexed runs in ~2s.prefix_len=0= old full scan.cum/et+ museum/collection scaffolding. Recovers ~70 inscriptions scoring just under threshold (Clusium cum agro,Clusii in museo publico→ Clusium 1.0).Clusino GA.→lake Clusinus,Parisiis→Parsiana,in fronte DA.).Coverage sweep
Open precision gaps (documented, not threshold-fixable)
Place-type disambiguation (prefer settlements over lakes/rivers) and non-findspot string filtering (catalogue sigla, pure museum provenance).
31 gazetteer tests pass (+4).
docs/PELAGIOS.mdupdated with the sweep.🤖 Generated with Claude Code