Repository navigation
Conversation
This branch has not been deployed
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.
Generated register-shaped entities and export them for entity resolution Addresses, company names and people are now generated from distributions measured on two real company registers rather than from Faker defaults:
addresses are shared on a Zipf curve, names carry the register's legal forms and spellings, and 4.5% of companies have anybody attached at all.
graphfaker register reads a register in Senzing format from a file, directory or zip, and --sink senzing writes a generated one back out with senzing/entities.parquet as the answer key. Scored with graphfaker.resolve: the name alone gives 0.93 F1, adding the address costs recall, and matching on address alone gives 0.03 precision.
Corrects an earlier claim: the 86.7% name collision rate counted records rather than companies, so it conflated one company written many times with two companies sharing a name. Per company it is 1%.
Also fixes: gen --export crashed on a Windows console, the DuckDB property graph failed on a dataset with no edges, and the benchmark's name normaliser never stripped L.L.C.