AI and Data Science Master the art of data science. Join now
Hope you are well.
I have a question I am hoping you can provides some insights into...
We are trying to use relations to extract multiple rows from an ingested document.We are using a "class" entity and then multiple attributes / entities which relate to the "class" entity.Our class entity is "PolicyHolder" and it has multiple attributes / entities related to it e.g. First_Name, Last_Name, Mobile_Number, Address etc.Currently we use a single relation for relating all the entities to the PolicyHolder class e.g. "PolicyHolder_HasA" and our WKS model is at 49% F1 score for relations with around 100 documents trained of less than 100 words each.Would it improve our relation F1 score if we named each relation uniquely wrt the related entity / attribute e.g. for First_Name the relation could be called "PolicyHolder_First_Name" and for Last_Name perhaps "PolicyHolder_Last_Name" etc. i.e. would this allow the wks nlu model to differentiate the relations better?Thank youAlessandro
Thanks so much – I appreciate your advice !
Sorry but you answered another question we are also grappling with �� probably because I ramble – apologies.
My original question in this thread is specifically related to the RELATIONS between the entities i.e. would you advise we use uniquely named RELATIONS between an Entity Class and Entity Attributes to achieve higher F1 scores on RELATION extraction because currently we use the same RELATION name for all attributes of a single class i.e. POLCY_HOLDER class "HAS_A" relation to first_name and "HAS_A" relation Last_name" or should we rather do POLICY_HOLDER class "HAS_A_First_Name" relation and "HAS_A_Last_Name" relation ?
Many thanks again for your inputs sir
You can also get more informaation