Unfairness towards subjective opinions in Machine Learning

Unfairness towards subjective opinions in Machine Learning

Agathe Balayn A.M.A.Balayn@tudelft.nl Delft University of Technology, IBM Center for Advanced Studies Alessandro Bozzon a.bozzon@tudelft.nl TU Delft, Web Information SystemsVan Mourik Broekmanweg 6Delftthe Netherlands  and  Zoltán Szlávik zoltan.szlavik@nl.ibm.com IBM Center for Advanced StudiesJohan Huizingalaan 765Amsterdamthe Netherlands
Abstract.

Despite the high interest for Machine Learning (ML) in academia and industry, many issues related to the application of ML to real-life problems are yet to be addressed. Here we put forward one limitation which arises from a lack of adaptation of ML models and datasets to specific applications. We formalise a new notion of unfairness as exclusion of opinions. We propose ways to quantify this unfairness, and aid understanding its causes through visualisation. These insights into the functioning of ML-based systems hint at methods to mitigate unfairness.

journalyear: 2019copyright: rightsretainedconference: CHI 2019: Human-Centered Machine Learning Perspectives Workshop; May 04, 2019; Glasgowdoi: isbn:

1. Introduction

achine Learning, unfairness, subjectivity, bias, toxicity prediction

Machine Learning (ML) is increasingly employed in real-life applications. Originally used to classify various types of samples based on objective labels, it is now also employed for classification tasks of subjective labels (see sidebar) (O’Neil, 2017; Skirpan and Gorelick, 2017). In such tasks, samples can not be associated with clear unique ground truth labels since the property to be assessed (and predicted) is subjective, and might therefore

itemize

digit recognition from images (LeCun et al., 1990),

human activity recognition from videos (Herath et al., 2017),

spam filtering from text (Almeida et al., 2016).

Subjective classification tasks:

  • violence of a video segment (Schedl et al., 2015),

  • aesthetic of an image (Bianco et al., 2016),

  • sentiment of a sentence (Tang et al., 2015b),

  • toxicity of a sentence (Wulczyn et al., 2017).

Opinion diversity in subjective tasks:

Table 1 (below) illustrates the diversity of annotators’ opinions on toxicity, which would be ignored in a traditional single-label dataset. 61% of the samples in the dataset bear disagreements for binary annotations, and even more for a 5-point Likert scale.

sample annotations
\midrule[2pt] \pbox0.28Is there perhaps enough newsworthy information to make an article about the Bundy family as a whole, that the various family members can be redirected to? Or does that violate a guideline I’m not aware of? \pbox0.08NT(100%)
\midrule[0.5pt] \pbox0.28What shit u talk to me, communist rat? \pbox0.08T(100%)
\midrule[0.5pt] \pbox0.28Please relate the ozone hole to increases in cancer, and provide figures. Otherwise, this article will be biased toward the environmentalist anti-CFC point of view instead of being neutral. \pbox0.08T(20%) NT(80%)
\midrule[0.5pt] \pbox0.28The article is true, the Israeli policies are killing Arab children. \pbox0.08T(50%) NT(50%)
Table 1. Example samples and annotations of an ML dataset for the task of predicting sentence toxicity (T: toxic, NT: non-toxic).

be subject to biases or differences in perception and interpretation from each individual assessor of the dataset. We argue that this shift of focus has a potential negative impact on the end-users of the applications whose opinions/perspectives might not be reflected by the system when they have not been captured in the data or/and in the model’s outputs. Specifically, we claim that the traditional way of conceiving ML-based systems is not adapted to the cases of subjective classifications, and that it leads to unfairness towards certain end-users but also to potential dangers towards society as a whole. Although the impact concerns end-users, we use interchangeably assessors and end-users since we measure its magnitude based on the assessors’ data used as a proxy for the end-users’ data that are not available in the dataset. The issue concerning differences between the assessors and end-users populations is relevant, but not within the scope of this work.

ML models usually output a single label per input representing a single opinion (often the majority one) or the averaged opinion (in case of numerical labels) which might not correspond to any individual. Outputting this label (or its distribution) might not be sufficient depending on the application. First, it conducts to ignoring part of the users’ opinions in potentially different proportions. That makes certain users’ experience of the system less valued than for others and can be perceived as unfairness towards these end-users whose opinions might never be showcased. Second, always ignoring certain opinions, mostly from the minority, and accounting for specific opinion trends contribute to the reinforcement of filter bubbles on the Web. This is an emergent danger for societies (Bozdag and van den Hoven, 2015).

We name this issue unfairness as a notion of opinion exclusion and define it as an inequality of inclusion of the opinions of the users in the outputs of the ML system. We put forward that, by resolving it, it would be possible to minimise potential negative effects coming from the applications of the systems both on a user and society level. In the following, we propose an initial strategy to evaluate and mitigate this unfairness, that we expose through the example of an ML model trained to predict whether a sentence is toxic or not. Yet the work is applicable to any subjective classification task.

3. Causes of unfairness along the ML pipeline

Looking deeper into the traditional ML pipeline, we identified three elements which contribute to causing unfairness, that all have to be addressed (Figure 1).

Algorithmic bias: ML research tackling the classification of subjective properties simply considers that the task can be represented using unique binary labels ignoring the subjectivity (Bianco et al., 2016; Tang et al., 2015b) sometimes removing the data with the most disagreement, and aggregating the rest. Soft labels are also employed (Sharmanska et al., 2016; Wulczyn et al., 2017) to account for the opinion diversity but this does not enable to identify the opinion of each individual. Only one paper (Binns et al., 2017) has considered the opinions of different categories of population (male and female) but it was shown that there is also disagreement within the categories. We suggest the whole problem to be re-framed in order to address unfairness. Here we do not wish to output one label for one sample, but one label for an input being the data sample and the specific user of the application (Figure 2).

Figure 1. The sources of unfairness in the traditional ML pipeline.
\Description

The sources of unfairness in the traditional ML pipeline. We show 3 sources of unfairness in the following order. During the dataset collection part, a dataset bias arises from crowdsourcing. During the design of the ML model, an algorithmic bias arises from the way the model is set-up. During the evaluation part, an evaluation bias arises from the fact that usual evaluation methods only focus on accuracy-related performance.

Figure 2. Traditional ML task and re-framed problem.
\Description

The traditional and re-framed ML problem. The traditional model takes as input a sample and output a label which is judged correct or not by the users of the model. In the reframed problem, the model takes as input a sample and a user, and output a label which corresponds to the opinion of the specific user on the sample.

he re-framed problem, we advocate for outputting one label for each input tuple consisting of a sample and an end-user. During the training phase, this corresponds to tuples of samples and assessors.

In this way, the creators of the application would have access to the opinion of each individual user and they could adapt the decision making process within the system not only to the data sample but to the user as well. For instance in social media, where one would wish to filter out toxic sentences, for each end-user we would not hide information that they, individually, might not see as non-toxic, but they would be protected from what they individually might perceive as toxic (e.g. in cases where a child and an adult do not have the same perception of sentence toxicity).

Dataset bias: The way of creating datasets tends to bias the data towards certain types of opinions. Since models are trained on these data, their outputs are automatically unfair. Besides, they are tested on the same type of data and consequently the unfairness might be missed. Indeed, most ML datasets have their labels collected via crowdsourcing (annotators label samples reflecting their opinions on these), which should enable the collection of true opinions. However, due to annotation quality issues (mistakes, spamming), researchers and practitioners need to exclude low quality inputs, but current methods can not distinguish these from low popularity opinions, and lead to the selection of only one opinion per sample, leading to exclusion. Indeed to avoid the problem, several annotators label a sample and the annotations are aggregated into a unique, more accurate label (e.g. by majority-voting -MV or by a probabilistic approach (Raykar et al., 2010; Whitehill et al., 2009)), assuming that the more annotators there are the higher the chance is to get a majority of correct annotations. This implies that correct labels are labels on which annotators agree, but subjectivity involves disagreement and consequently the assumption does not hold (example Table 1). Thus, this process automatically biases datasets towards a unique kind of opinion reflected via the aggregation method selected. Few works leverage the disagreement to filter out the wrong annotators and annotations. The CrowdTruth framework enables to compute quality scores to quantify the annotators’ quality and the samples’ ambiguity based on their disagreement (Aroyo and Welty, 2013). Collaborative approaches of discussion and argumentation between annotators are also taken to refine the crowdsourcing task and get high-quality labels (Chang et al., 2017; Drapeau et al., 2016), but this still implies a unique ground truth. Groups of annotators with similar annotation trends can also be identified by clustering to possibly discover annotators of high-quality or having specific interpretations of the tasks, but this is not yet scalable to a large number of annotators annotating different samples (Kairam and Heer, 2016).

Evaluation bias: The notion of fairness as exclusion of opinions being new, there is no established way to evaluate it. Previous research is directed at unfairness as a notion of discrimination towards protected categories of population, focusing on models which classify people over certain labels (e.g. whether someone who committed a crime will reoffend) (Gajane and Pechenizkiy, 2017). Recently, research has also studied unfairness in the ML process (mainly the choice of possibly unfair features) (Grgic-Hlaca et al., 2018). Consequently, current systems’ evaluation methods are biased towards performance metrics and unfairness as discrimination. The lack of adapted metric fosters exclusion in current systems since ML practitioners are not aware of the problem, or have no tool to consider it in their systems. Therefore, we advocate for investigating the evaluation of unfairness and propose initial research ideas in the next sections.

4. Methods to understand and mitigate unfairness

enumerate

Quantifies unfairness.

Quantifies general model performance (to observe the trade-off between fairness and performance since a model could be totally fair and inaccurate).

Is independent from the evaluation dataset.

Is adaptable to the performance metric(s) important for the application.

Provides insights into causes of unfairness.

Grouping criteria to understand unfairness.
We assume that the main reason for which unfairness can occur is the difficulty of ML models to predict certain opinions (generally the uncommon opinions). This difficulty might manifest in multiple ways that can be investigated through the following grouping settings.

  • [leftmargin=*]

  • Sample-level: Ambiguous samples might present more disagreement making the opinions on them harder to discover by the model. Grouping samples based on their ambiguity would point out these difficulties.

  • Annotation-level: Popular annotations for a sample are seen more often by the ML model during training, and consequently, should be easier to predict. Grouping annotations based on their popularity (percentage of identical annotations within a sample’s annotations) would highlight this.

  • User-level: Apart from the disagreement among users, users of a certain category of population might have similar opinions. Grouping these users would show whether certain categories are discriminated against for the benefit of others.

4.1. Our proposition to identify and quantify unfairness in ML

Here we define an ML model to be unfair when its performance is unequal across its users (opinions would not be equally accounted for among users). Although this definition suggests easy ways to identify whether a model is unfair, we also need 1) to quantify unfairness in order to minimise it and to compare models on other criteria than traditional performance measures, and 2) to investigate potential causes of unfairness.

To quantify unfairness, a metric should satisfy the requirements listed in the sidebar. We propose the following evaluation method. a) Group the users of the model in the dataset based on their disagreement rate with the other users (we compute the average disagreement rate -ADR- per user as the percentage of times a user’s annotations are different from the MV because we assume the MV is representative of the outputs of the traditional unfair ML model). This enables to obtain comparable values for different datasets which would be constituted of the same groups’ characteristics. b) Compute model performance for each user, and the mean of these values within each group. c) Compute the standard deviation and mean across the groups’ performance to quantify unfairness and general model performance, respectively. The performance metric is chosen by the ML practitioner and several metrics can be combined by averaging the results.

To investigate potential causes of unfairness, we visualise the performance of each individual group. We hypothesize it enables to identify where inequalities come from and to point out the types of users for which the predictions should be improved. Additionally, we suggest other criteria (see sidebar) to group the dataset in order to better understand how the ML model behaves and which are the inaccuracies that make the model unfair.

4.2. Considerations to decrease unfairness

To mitigate dataset bias and maintain a diversity of opinions, we must not aggregate the annotations. We propose first to use a quality control mechanism (e.g. CrowdTruth framework) to filter out the lowest quality annotators giving wrong annotations. Second, we can employ disagreement as a signal to identify valid but unpopular opinions and differentiate them from occasional annotators’ mistakes.

Regarding algorithmic bias, we envision two main lines of work which could eventually be combined. Usually, few data points per user are known at training time, thus it is neither possible nor scalable to train one accurate model per user. A solution is to train models with certain parameters conditioned on the users (e.g. (Tang et al., 2015a) for recommender systems), where preferences of new users should be learned at run time. Another possibility is to leverage the knowledge of other fields such as Psychology to find the internal characteristics of a user, which influence their perception of a label (or deduce these variables with additional ML models) and input these as features encoding each user.

4.3. Examples for sentence toxicity prediction

sidebar

Model 1 Model 2
\midrule[2pt] \pbox0.06Inputs samples \pbox0.15samples + demographics
\pbox0.15Ground truth MV annotations
Unfairness value
0.07 0.04
General performance
0.68 0.68
Table 2. First two ML models used to analyse the unfairness evaluation method.

dd the demographic information to Model 2’s inputs because Psychology literature highlights these variables as the most influencing variables for perception of sentence toxicity (Cowan and Hodge, 1996). Model 3 is a hypothetical, perfectly accurate model which returns the exact annotations for each annotator, and consequently, is fair.

We instantiate the models with Logistic Regression classifiers trained and tuned using 5-fold cross validation, and compute the accuracy performance on a balanced evaluation dataset.

Figure 3. Visualisation of the unfairness based on groups of annotators’ average disagreement rate with the MV (ADR).
\Description

Visualisation of the unfairness based on groups of annotators’ average disagreement rate with the MV (ADR). In each row we see the performance accuracy of the two models on the different group of annotators. Model 2’s performance are more equal across rows than model 1’s performance.

We illustrate our method for a better understanding of unfairness using the dataset of (Wulczyn et al., 2017) for sentence toxicity prediction, which includes opinions of ten annotators per sample with corresponding demographic information (age, gender, education). We build three ML models with three different unfairness-related behaviors (see sidebar). Models 1 to 3 are expected to be less to most fair due to their training process. Figure 3 shows an example visualisation of the groups’ performance for annotators grouped on ADR scores. As expected, Model 1 is more unfair than Model 2 since its performance across groups is more disparate than for Model 2. The perfect model would present equal accuracy of 1 for each group and consequently an unfairness of 0 and performance of 1. The unfairness score (Table 2) reflects this trend with a higher value for Model 1, while the general performance is equal for the two models. The visualisation furthermore confirms the sources of unfairness in the models. We observe that Model 1 is inaccurate at predicting the opinions of users who tend to disagree with the MV the most; this is better in Model 2, but not fully solved. ML practitioners could use these observations to further improve their model, for example, by collecting more data from specific annotators.

4.4. Discussion

The evaluation method meets the requirements to better understand unfairness. Although applied to a specific case focusing on accuracy with Logistic Regression, it is applicable to any type of subjective classification task, any performance metric(s) as well as ML model. To thoroughly evaluate the effectiveness of the method in the future, we recommend first to perform user studies to understand whether the visualizations are both clear and informative to the users, and second to investigate whether integrating the visualizations within a human-in-the-loop unfairness mitigation methodology enables to effectively remove the biases. Our proposition accounts for group fairness. However, there might exist unfairness inside the groups themselves, and thus, metrics to measure individual fairness would also give different insights into the problem. Unsupervised clustering of sentences with similar content, or of annotators with similar annotation trends could enable the discovery of other reasons for unfairness. E.g. it could identify annotators with a certain opinion trend, which might always be served badly by a model compared to annotators of another opinion line. Besides, we employed users’ demographics to improve classification, however, this might be a privacy sensitive point for certain applications. Here appears a trade-off not only between fairness and accuracy, but also privacy, that presages more complexity in the ways to mitigate the issue.

5. Conclusion

In this paper, we discussed the issue of unfairness in the context of ML-based systems, and we argued for a reconsideration of the problem at hand in other terms with more attention towards the human user. We proposed ways to quantify unfairness, to explore its causes, and to mitigate them. The proposed approach is currently being implemented within the IBM AIF360 toolkit (Bellamy et al., 2018), in order to make it easily available for ML practitioners who would implement systems with potential ethical issues. This work falls within the broader research direction of ethics, ML and explainability. Methods to make ML more fair might trigger additional ethical issues that remain to be investigated.

References

  • T. A. Almeida, T. P. Silva, I. Santos, and J. M. G. Hidalgo (2016) Text normalization and semantic indexing to enhance instant messaging and sms spam filtering. Knowledge-Based Systems 108, pp. 25–32. Cited by: §1.
  • L. Aroyo and C. Welty (2013) Crowd truth: harnessing disagreement in crowdsourcing a relation extraction gold standard. WebSci2013. ACM 2013. Cited by: §3.
  • R. K. E. Bellamy, K. Dey, M. Hind, S. C. Hoffman, S. Houde, K. Kannan, P. Lohia, J. Martino, S. Mehta, A. Mojsilovic, S. Nagar, K. N. Ramamurthy, J. Richards, D. Saha, P. Sattigeri, M. Singh, K. R. Varshney, and Y. Zhang (2018) AI Fairness 360: an extensible toolkit for detecting, understanding, and mitigating unwanted algorithmic bias. Cited by: §5.
  • S. Bianco, L. Celona, P. Napoletano, and R. Schettini (2016) Predicting image aesthetics with deep learning. In International Conference on Advanced Concepts for Intelligent Vision Systems, pp. 117–125. Cited by: 2nd item, §3.
  • R. Binns, M. Veale, M. Van Kleek, and N. Shadbolt (2017) Like trainer, like bot? inheritance of bias in algorithmic content moderation. In International Conference on Social Informatics, pp. 405–415. Cited by: §3.
  • E. Bozdag and J. van den Hoven (2015) Breaking the filter bubble: democracy and design. Ethics and Information Technology 17 (4), pp. 249–265. Cited by: §1.
  • J. C. Chang, S. Amershi, and E. Kamar (2017) Revolt: collaborative crowdsourcing for labeling machine learning datasets. In Proceedings of the 2017 CHI Conference on Human Factors in Computing Systems, pp. 2334–2346. Cited by: §3.
  • G. Cowan and C. Hodge (1996) Judgments of hate speech: the effects of target group, publicness, and behavioral responses of the target. Journal of Applied Social Psychology 26 (4), pp. 355–374. Cited by: §4.3.
  • R. Drapeau, L. B. Chilton, J. Bragg, and D. S. Weld (2016) Microtalk: using argumentation to improve crowdsourcing accuracy. In Fourth AAAI Conference on Human Computation and Crowdsourcing, Cited by: §3.
  • P. Gajane and M. Pechenizkiy (2017) On formalizing fairness in prediction with machine learning. Cited by: §3.
  • N. Grgic-Hlaca, E. M. Redmiles, K. P. Gummadi, and A. Weller (2018) Human perceptions of fairness in algorithmic decision making: a case study of criminal risk prediction. In Proceedings of the 2018 Conference on World Wide Web, pp. 903–912. Cited by: §3.
  • S. Herath, M. Harandi, and F. Porikli (2017) Going deeper into action recognition: a survey. Image and vision computing 60, pp. 4–21. Cited by: §1.
  • S. Kairam and J. Heer (2016) Parting crowds: characterizing divergent interpretations in crowdsourced annotation tasks. In Proceedings of the 19th ACM Conference on Computer-Supported Cooperative Work & Social Computing, Cited by: §3.
  • Y. LeCun, B. E. Boser, J. S. Denker, D. Henderson, R. E. H, W. E. Hubbard, and L. D. Jackel (1990) Handwritten digit recognition with a back-propagation network. In Advances in neural information processing systems, pp. 396–404. Cited by: §1.
  • C. O’Neil (2017) Weapons of math destruction: how big data increases inequality and threatens democracy. Broadway Books. Cited by: §1.
  • V. C. Raykar, S. Yu, L. H. Zhao, G. H. Valadez, C. Florin, L. Bogoni, and L. Moy (2010) Learning from crowds. Journal of Machine Learning Research 11 (Apr), pp. 1297–1322. Cited by: §3.
  • M. Schedl, M. Sjöberg, I. Mironica, B. Ionescu, V. L. Quang, and Y. Jiang (2015) Vsd2014: a dataset for violent scenes detection in hollywood movies and web videos. Sixth Sense 6 (2.00), pp. 12–40. Cited by: 1st item.
  • V. Sharmanska, D. Hernández-Lobato, J. Miguel Hernandez-Lobato, and N. Quadrianto (2016) Ambiguity helps: classification with disagreements in crowdsourced annotations. In Proceedings of the IEEE Conference on Computer Vision and Pattern Recognition, Cited by: §3.
  • M. Skirpan and M. Gorelick (2017) The authority of” fair” in machine learning. Cited by: §1.
  • D. Tang, B. Qin, T. Liu, and Y. Yang (2015a) User modeling with neural network for review rating prediction.. In IJCAI, pp. 1340–1346. Cited by: §4.2.
  • D. Tang, B. Qin, and T. Liu (2015b) Document modeling with gated recurrent neural network for sentiment classification. In Proceedings of the 2015 conference on empirical methods in natural language processing, pp. 1422–1432. Cited by: 3rd item, §3.
  • J. Whitehill, T. Wu, J. Bergsma, J. R. Movellan, and P. L. Ruvolo (2009) Whose vote should count more: optimal integration of labels from labelers of unknown expertise. In Advances in neural information processing systems, Cited by: §3.
  • E. Wulczyn, N. Thain, and L. Dixon (2017) Ex machina: personal attacks seen at scale. In Proceedings of the 26th International Conference on World Wide Web, Cited by: 4th item, §3, §4.3.
Comments 0
Request Comment
You are adding the first comment!
How to quickly get a good reply:
  • Give credit where it’s due by listing out the positive aspects of a paper before getting into which changes should be made.
  • Be specific in your critique, and provide supporting evidence with appropriate references to substantiate general statements.
  • Your comment should inspire ideas to flow and help the author improves the paper.

The better we are at sharing our knowledge with each other, the faster we move forward.
""
The feedback must be of minimum 40 characters and the title a minimum of 5 characters
   
Add comment
Cancel
Loading ...
397190
This is a comment super asjknd jkasnjk adsnkj
Upvote
Downvote
""
The feedback must be of minumum 40 characters
The feedback must be of minumum 40 characters
Submit
Cancel

You are asking your first question!
How to quickly get a good answer:
  • Keep your question short and to the point
  • Check for grammar or spelling errors.
  • Phrase it like a question
Test
Test description