Repository navigation
feat: let a field config exclude mislabelled records - #42
Merged
Merged
Conversation
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
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.
Closes #41
What
exclude_worksin the field config: OpenAlex records dropped at cleaning, with their edges.stats.jsoncounts them asexcluded_nodes.gnn.yamlexcludesW2964015378. It is cited 2,347 times inside the expanded graph, more than GCN, but titled and dated as a 2025 vulnerability-detection paper.Why
No rule can tell a record's title is wrong. Without the exclusion it would rank as an originator of most GNN-era papers, under a name that is not its own. Keeping the list in the field config keeps field-specific knowledge in
fields/.Verify
uv run pytest tests/test_build.py tests/test_config.py uv run python -m graph.build --field gnn --data-dir data/expanded # excluded_nodes 1Generated with Claude Code