Page MenuHomePhabricator

Jade UI should provide the target's ORES score, and a human-readable explanation
Closed, DeclinedPublic

Description

Some research has shown that end-users will provide better labels, will have higher trust in the system, and communication will be improved if our system includes an explanation of how ORES arrived at its scores. We should provide these explanations whenever Jade is requesting judgment about a score.

The ideal explanation will include these elements (see the link above for details):

  • Uncertainty level
  • Sufficient low-level context
  • ORES prediction

How to display the low-level context is an interesting problem and is the only non-trivial aspect of this task. We don't want to display all of the features, but only the ones most important to how ORES arrived at its score.

The key low-level features should be displayed in a way that the user can agree or disagree with each one. This can be split into future work if it turns out to be difficult.

Event Timeline

See the exploratory LIME work in T196475.

Wouldn't this be an ORES feature rather than a JADE feature?

awight renamed this task from JADE UI should provide an explanation of the target ORES score to JADE UI should provide the target's ORES score, and a human-readable explanation.Nov 14 2018, 11:07 PM
awight moved this task from Radar to Feature Requests on the Jade board.
Harej lowered the priority of this task from Medium to Low.Nov 14 2018, 11:57 PM

I'm curious about the reasoning behind descoping, or how this will fit into our plans in the future? Happy to support scope reduction in general, but this seems like an important feature for the ORES false-positive use case…

It doesn't seem like this is well described. It looks like this task is about implementing a LIME-like thing for ORES on top of JADE.

Maybe you (@awight) could make the description more specific and that could be grounds for re-scoping?

Earlier discussion on this task suggests that it got de-prioritized because it's more of a feature for ORES than for Jade, but really it can go either way. I think it's a feature of ORES (figuring out how exactly to reveal its inner workings to the outside) but also a feature of Jade (the actual visualization step).

I'm thinking of this more and I am temped to decline the task. I am not sure presenting ORES scores in Jade is a good idea at all. A common usage pattern for ORES, namely the article quality model, is to take the article quality score ORES puts out and then use that to update the WikiProject assessment template. This creates a feedback loop. If we put ORES scores directly into the Jade interface, I am not convinced people won't just copy and paste those scores into Jade and then call it a job done. I really want to do as little as possible to prime people's thinking if the goal is to truly get human feedback.

Harej renamed this task from JADE UI should provide the target's ORES score, and a human-readable explanation to Jade UI should provide the target's ORES score, and a human-readable explanation.Apr 15 2019, 10:17 PM
Harej updated the task description. (Show Details)
Aklapper lowered the priority of this task from Low to Lowest.May 23 2021, 10:54 PM