This issue is to suggest that we treat subclass_of edges, similar_to edges, and related ones in the same manner as we treat occurs_together_in_literature_withedges, meaning that we return them in the answer subgraphs, but not as nodes/edges in the answer results, and probably not consider those metrics as part of the scoring/ranking. I understand why we added those edges, but they feel more like node properties or supporting evidence to me, not "knowledge" that is returned in response to a user query.
For example, this result set dilutes the user intention and any meaningful results:
Alternatively, or in addition to, perhaps we can support a feature that allows users to "turn off" subclassing or specific predicates? That might be the easier option.
karafecho
commented
3 hours ago
This issue is to suggest that we treat
subclass_ofedges,similar_toedges, and related ones in the same manner as we treatoccurs_together_in_literature_withedges, meaning that we return them in the answer subgraphs, but not as nodes/edges in the answer results, and probably not consider those metrics as part of the scoring/ranking. I understand why we added those edges, but they feel more like node properties or supporting evidence to me, not "knowledge" that is returned in response to a user query.For example, this result set dilutes the user intention and any meaningful results:
Alternatively, or in addition to, perhaps we can support a feature that allows users to "turn off" subclassing or specific predicates? That might be the easier option.
Note that this issue is related to #139 and #194.