@benestar_wm Cool, thanks for the help again and for fixing it for the future :-)
@benestar_wm The error message was a bit misleading. Maybe something like “Property $p expects values of type $t, but type $s was sent”.
@benestar_wm #FacePalm, from all possible properties I randomly chose a one that doesn’t accept entities. Thanks, working now :-)
@benestar_wm Already done that. I don’t get what’s wrong. pastebin.com/TqRMyqMT
@benestar_wm @wikidata Could you have a look what I’m doing wrong here? http://t.co/1fT8NwaGev Trying wbcreateclaim https://t.co/1qXGwM6R05
#AAAI Spring Symposium. “If you’re the smartest person in the room […]â€â€”I’m in the right room… http://t.co/kL86YQ4Gw2 http://t.co/sk12S9qYAf
@wikidata Is there heavy caching in place for the API? Don’t see my changes in the JSON: https://t.co/BxlshMTpXs
@ghirardinicola Not yet, still in active development, sorry. Just sharing status updates… Watch this space for the actual tool release, tho.
The @FBaseEâ@wikidatata migration tool now supports migrating single sources, properties w/ sources, & full statementspic.twitter.com/zSaajP1Lhbhb
@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.