@benestar_wm It’s give & take ;-) I guess one could move the @fbase sources over to the @wikidata source. Even more manual, but justifiable.
@benestar_wm This because upon manual inspection I saw that from the Mercedes item you can infer the corresponding country.
@benestar_wm In this very case I’d reject the less precise new @fbase value (Uruguay) & leave the more precise @wikidata value (Mercedes).
@benestar_wm Luckily we settled for human curation: “The editor will be able to confirm […]”—https://t.co/rxq0WEm4f1
@benestar_wm Think the general case. There may be gaps in the rel. chain. It’s obviously easy in the concrete case, but IMHO not generally.
@benestar_wm Easy for whom? For a human or a machine? It’s a classic HIT (human intelligence task) I guess… Hard for machines.
@RubenVerborgh I agree, but can see where they were coming from. Found this https://t.co/aZXmKxgd3E and this https://t.co/ttWJ2B4t3E.
Discovered the JavaScript code style checker @jscs_dev via @JSHint’s maxlen deprecation alert… Immediate alias: jscs=’jscs —preset=google’.
Classic merge issue: @fbase says place of birth Uruguay [2 ref.], @wikidata says Mercedes (city in Uruguay) [1 ref.]. pic.twitter.com/0ubWTM19HL