Papers › A Synthetic Dataset for Personal Attribute Inference

A Synthetic Dataset for Personal Attribute Inference

11 Jun 2024arXiv:2406.07217archive 2025-07-28

Hanna Yukhymenko, Robin Staab, Mark Vero, Martin Vechev

Recently, powerful Large Language Models (LLMs) have become easily accessible to hundreds of millions of users world-wide. However, their strong capabilities and vast world knowledge do not come without associated privacy risks. In this work, we focus on the emerging privacy threat LLMs pose -- the ability to accurately infer personal information from online texts. Despite the growing importance of LLM-based author profiling, research in this area has been hampered by a lack of suitable public datasets, largely due to ethical and privacy concerns associated with real personal data. We take two steps to address this problem: (i) we construct a simulation framework for the popular social media platform Reddit using LLM agents seeded with synthetic personal profiles; (ii) using this framework, we generate SynthPAI, a diverse synthetic dataset of over 7800 comments manually labeled for personal attributes. We validate our dataset with a human study showing that humans barely outperform random guessing on the task of distinguishing our synthetic comments from real ones. Further, we verify that our dataset enables meaningful personal attribute inference research by showing across 18 state-of-the-art LLMs that our synthetic comments allow us to draw the same conclusions as real-world data. Combined, our experimental results, dataset and pipeline form a strong basis for future privacy-preserving research geared towards understanding and mitigating inference-based privacy threats that LLMs pose.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 6 code samples harvested from 2 repositories linked to this paper: 5 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 4 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 4 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 1 sample from 1 repository, 1 ran (1 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 5 samples from 1 repository, 4 ran (0 with no instrument failure; 4 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

eth-sri/synthpai officialmentioned in papermentioned on GitHubSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 unverified report
eth-sri/llm-anonymization mentioned on GitHubMITSyntology: 5 samples, 4 ran (4 instrument-failed) · 1 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

6 samples harvested: 5 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 4 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
4ran · our draft was wrong
1unverified

Licence: 0 of the 6 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

eth-sri/synthpai official repository 1 sample, 1 ran (0 instrument-failed) · 0 unverified
compare_ages src/thread/eval_thread.py ran · honoured contract fingerprinted MIT (permissive) · 63e3f3bd138014ac · report fixture: signature age1:str/0/str, age2:str/0/str, threshold:float/0/float · returned int · level recorded 2026-09-22
eth-sri/llm-anonymization community (archive-listed) 5 samples, 4 ran (4 instrument-failed) · 1 unverified
get_paths in 32 papers src/anonymized/plot_anonymized.py ran · our draft was wrong MIT (permissive) · a0936369faa9744b · report fixture: signature type:str/0/str · returned list · level recorded 2026-09-24
load_data_from_paths src/anonymized/plot_anonymized.py ran · our draft was wrong MIT (permissive) · 5efab7bf520d5b17 · report fixture: signature paths:list/1/str · returned DataFrame · level recorded 2026-09-24
method_to_name src/anonymized/plot_anonymized.py ran · our draft was wrong MIT (permissive) · 430e64bbf8eabbfc · report fixture: signature method:str/0/str · returned str · level recorded 2026-09-24
parse_utility_answer src/anonymized/anonymized.py ran · our draft was wrong fingerprinted MIT (permissive) · eb6a12d058783ffd · report fixture: signature answer_str:str/0/str · returned dict · level recorded 2026-09-24
prompt_user src/anonymized/evaluate_anonymization.py unverified MIT (permissive) · cfa3ed61b3c34083 · report

Tasks

AttributeAuthor ProfilingPersonality Trait RecognitionPrivacy PreservingSynthetic Data GenerationWorld KnowledgeZero-shot Classification (unified classes)

Datasets

Introduced by this paper, per the archive.

SynthPAI

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Personality Trait Recognition SynthPAI GPT-4 Average accuracy in % 77.9% #1 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI LLama-3 70B Average accuracy in % 72.2% #2 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI Mixtral 8x22B Average accuracy in % 72% #3 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI Claude-3 Opus Average accuracy in % 71.1% #4 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI Claude-3 Sonnet Average accuracy in % 70.9% #5 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI Gemini 1.5 Pro Average accuracy in % 67.5% #6 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI Qwen1.5 110B Average accuracy in % 65.7% #7 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI Gemini 1.0 Pro Average accuracy in % 64.6% #8 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI Claude-3 Haiku Average accuracy in % 64% #9 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI Yi 34B Average accuracy in % 57.7% #10 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI LLama-2 70B Average accuracy in % 56.8% #11 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI GPT-3.5 Average accuracy in % 55.9% #12 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI LLama-3 8B Average accuracy in % 53.5% #13 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI Mixtral 8x7B Average accuracy in % 52.3% #14 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI LLama-2 13B Average accuracy in % 48.7% #15 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI Mistral 7B Average accuracy in % 42.4% #16 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI Gemma 7B Average accuracy in % 34.9% #17 of 18 Archive leaderboard report
Personality Trait Recognition SynthPAI LLama-2 7B Average accuracy in % 33% #18 of 18 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

CoT PromptingFocus

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections