We have support for the organismOrdering preference, which allows the user to specify his preference w.r.t. close matches (currently only ties). It would be good to also allow for a typeOrdering preference, which would work in a similar way: A tie can be broken by the specified ordering of entity types.
Consider two matches, both with the name "X":
They both match the search string "X" perfectly, so we can use the typeOrdering: ['protein', 'chemical'] preference to break the tie by putting the protein first. Text mining systems like REACH are good at providing type hints like this, but they aren't good at providing the correct grounding. So we can use the information provided by REACH for typeOrdering on a per-entity basis, similar to how we use the information provided by REACH for organismOrdering on a per-paper basis.
We have support for the
organismOrderingpreference, which allows the user to specify his preference w.r.t. close matches (currently only ties). It would be good to also allow for atypeOrderingpreference, which would work in a similar way: A tie can be broken by the specified ordering of entity types.Consider two matches, both with the name "X":
They both match the search string "X" perfectly, so we can use the
typeOrdering: ['protein', 'chemical']preference to break the tie by putting the protein first. Text mining systems like REACH are good at providing type hints like this, but they aren't good at providing the correct grounding. So we can use the information provided by REACH fortypeOrderingon a per-entity basis, similar to how we use the information provided by REACH fororganismOrderingon a per-paper basis.