You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We train and test the model using 1-N scoring which is why we insert reciprocal relations, the same way as in Dettmers et al., 2018 (code) (reciprocal relations are also used by Lacroix et al., 2018 (code)): for each relation, we create an inverse by appending "_reverse" to the relation name. However, we train and test each triple only in one direction, always predicting the tail, i.e. (e_1, r, ?) and (e_2, r_reverse, ?), which is equivalent to not having reciprocal relations and predicting both head and tail.
This is different from having reciprocal relations in your training and test set, because in that case for each of them you would predict both head and tail, which would lead to an easier task and higher accuracy.
Reverse relation is usually removed from datasets, but you add it to training data? What is the motivation for this?
The text was updated successfully, but these errors were encountered: