Our first iteration of Meta ORES is probably going to be simple and limited to reviewing ORES scores. However, it will be immediately useful (T153150) to extend this concept to possibly provide it as a backend for wikilabels: people making collective judgment calls about commits, reverts, and admin actions. There might be even more interesting applications beyond this.
|Open||None||T166045 Scoring platform team FY18 Q1|
|Open||None||T166053 [Spike] potential technical implementations of ORES meta|
|Open||None||T148700 Meta ORES: UI/API for reviewing/refuting how ORES classifies you and your stuff|
|Open||None||T153145 Meta ORES: API data storage and querying|
|Open||None||T153152 Design Meta ORES data storage schema|
|Open||None||T153149 [Spec] Design meta ORES general wiki entity matching schema|
Maybe we need to brainstorm use cases before going too far down that road, but I think it's a solid beginning to have a table like you suggest, and "target entity" is just a row in this table. Then we have a graph that can be expanded to whatever schema is appropriate.