Papers › Hidden or Inferred: Fair Learning-To-Rank with Unknown Demographics

Hidden or Inferred: Fair Learning-To-Rank with Unknown Demographics

24 Jul 2024arXiv:2407.17459archive 2025-07-28

Oluseun Olulana, Kathleen Cachel, Fabricio Murai, Elke Rundensteiner

As learning-to-rank models are increasingly deployed for decision-making in areas with profound life implications, the FairML community has been developing fair learning-to-rank (LTR) models. These models rely on the availability of sensitive demographic features such as race or sex. However, in practice, regulatory obstacles and privacy concerns protect this data from collection and use. As a result, practitioners may either need to promote fairness despite the absence of these features or turn to demographic inference tools to attempt to infer them. Given that these tools are fallible, this paper aims to further understand how errors in demographic inference impact the fairness performance of popular fair LTR strategies. In which cases would it be better to keep such demographic attributes hidden from models versus infer them? We examine a spectrum of fair LTR strategies ranging from fair LTR with and without demographic features hidden versus inferred to fairness-unaware LTR followed by fair re-ranking. We conduct a controlled empirical investigation modeling different levels of inference errors by systematically perturbing the inferred sensitive attribute. We also perform three case studies with real-world datasets and popular open-source inference methods. Our findings reveal that as inference noise grows, LTR-based methods that incorporate fairness considerations into the learning process may increase bias. In contrast, fair re-ranking strategies are more robust to inference errors. All source code, data, and experimental artifacts of our experimental study are available here: https://github.com/sewen007/hoiltr.git

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 17 code samples harvested from 1 repository linked to this paper: 12 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 3 honoured, 1 violated, 6 with no contract checked; 2 where Syntology's instrument failed) · 5 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 17 samples from 1 repository, 12 ran (10 with no instrument failure; 2 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 on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

sewen007/hoiltr officialmentioned in paperApache-2.0Syntology: 17 samples, 12 ran (2 instrument-failed) · 5 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

17 samples harvested: 12 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 3 honoured, 1 violated, 6 with no contract checked; 2 where Syntology's instrument failed) · 5 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.

3ran · honoured contract
1ran · violated contract
2ran · our draft was wrong
6ran
5unverified

Licence: 0 of the 17 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 sewen007/hoiltr. “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.

sewen007/hoiltr official repository 17 samples, 12 ran (2 instrument-failed) · 5 unverified
MARC HOIRank/data_analysis/ARC.py ran · our draft was wrong Apache-2.0 (permissive) · 41a8fca30baa973d · report fixture: signature df1:DataFrame/0/?, df2:DataFrame/0/? · returned tuple · level recorded 2026-09-24
Z HOIRank/data_analysis/ValidInputs.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · 6aa8a03e240c13b8 · report fixture: signature k:int/0/int · returned float64 · level recorded 2026-09-24
Z_Vector HOIRank/data_analysis/ValidInputs.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · da9eb00bc46a9af2 · report fixture: signature k:int/0/int · returned ndarray · level recorded 2026-09-24
avg_pos_diff_ndcg HOIRank/data_analysis/avg_pos_dif.py ran · honoured contract Apache-2.0 (permissive) · 79146393cf59a664 · report fixture: signature r1:str/0/str, r2:str/0/str · returned float · level recorded 2026-09-24
avg_pos_diff_skew HOIRank/data_analysis/avg_pos_dif.py ran Apache-2.0 (permissive) · ccdafee51fd54c94 · report fixture: signature skew1:str/0/str, skew2:str/0/str, group:str/0/str · returned float · level recorded 2026-09-24
exposure_ratio HOIRank/data_analysis/avgExp.py ran fingerprinted Apache-2.0 (permissive) · 7b97ab5c1933e24d · report fixture: signature protected_exposure:Tensor/1/float, unprotected_exposure:Tensor/1/float · returned Tensor · level recorded 2026-09-24
extract_string HOIRank/data_analysis/calculate_metrics.py ran fingerprinted Apache-2.0 (permissive) · bb3886f125bb7628 · report fixture: signature input_string:str/0/str, start_string:str/0/str, end_string:str/0/str · returned str · level recorded 2026-09-24
get_files in 30 papers HOIRank/data_analysis/combine.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) · 434b485a4d4b996f · report fixture: signature directory:str/0/str, exclude_name:str/0/str · returned list · level recorded 2026-09-24
kT HOIRank/data_analysis/kendallTau.py ran · violated contract fingerprinted Apache-2.0 (permissive) · b4b069e72cf8355d · report fixture: signature X:ndarray/1/int, Y:ndarray/1/int · returned float64 · level recorded 2026-09-24
prob HOIRank/data_analysis/ValidInputs.py ran fingerprinted Apache-2.0 (permissive) · 2402d86e1a293756 · report fixture: signature a:Tensor/1/int, b:Tensor/1/int · returned Tensor · level recorded 2026-09-24
substring_match HOIRank/data_analysis/calculate_metrics.py ran Apache-2.0 (permissive) · d35a2badd140bf8e · report fixture: signature longstring1:str/0/str, longstring2:str/0/str, substring:str/0/str · returned bool · level recorded 2026-09-24
updated_value HOIRank/data_analysis/combine.py ran Apache-2.0 (permissive) · 7e62f90b778e354e · report fixture: signature old_value:float/0/float, new_value:float/0/float, count:int/0/int · returned float · level recorded 2026-09-24
NDCG HOIRank/data_analysis/NDCG.py unverified Apache-2.0 (permissive) · 214998a5c54ed783 · report
NDKL HOIRank/data_analysis/NDKL.py unverified Apache-2.0 (permissive) · 72afe6bc46003fb9 · report
avg_exp HOIRank/data_analysis/avgExp.py unverified Apache-2.0 (permissive) · 3a7ce8e8a2119f94 · report
dp_exp HOIRank/data_analysis/avgExp.py unverified Apache-2.0 (permissive) · c20e980dc033dd19 · report
skew in 21 papers HOIRank/data_analysis/skew.py unverified Apache-2.0 (permissive) · 47d147d4a32387a5 · report

Tasks

AttributeFairnessLearning-To-RankRe-Ranking

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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