Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confusion about the output (role type) #4

Closed
ZacBi opened this issue Mar 16, 2020 · 4 comments
Closed

Confusion about the output (role type) #4

ZacBi opened this issue Mar 16, 2020 · 4 comments

Comments

@ZacBi
Copy link

ZacBi commented Mar 16, 2020

  Hi, I have glanced through your paper and found the final output is the role type involved in the input sentence rather than the role type of candidate entity. Because you compress/encode the input embeddings to a sentence representation/embedding, then concatenate it with the role-oriented embedding before using a softmax to get the estimated role type.
  Besides, what if there are no explicit argument roles in the daily text? I mean, you can't get labeled sentence in testset, so you don't know which role types contained in the input sentence. How could I calculate the role-oriented embedding?
  Thank you for your explanation.

@wzq016
Copy link
Collaborator

wzq016 commented Mar 19, 2020

entity information is included in dynamic maxpooling stage and the output is for candidate entity.

In test stage, we calculate every roles and select role with highest score, so we didn't use label in test stage.

@ZacBi
Copy link
Author

ZacBi commented Mar 19, 2020

  Thanks for your response, but it doesn't clear my confusion. For your paper you said:

image

  In Logic Union Module you calculate a weighted average sum over all hidden states in the sentence to get a role-oriented embedding(context vector for each role).
  So, I understand that your method/framework can work if and only if an input sentence contained one candidate entity, otherwise it doesn't make sense. Perhaps, use dynamic max-pooling for each candidate entity to construct its own instance embedding x.

@wzq016
Copy link
Collaborator

wzq016 commented Mar 19, 2020

Hidden embeddings h is related with selected trigger and entity, since we feed position embedding to encoder together with word embedding. So role-oriented embedding is related with candidate entity.

@ZacBi
Copy link
Author

ZacBi commented Mar 19, 2020

Fine... it looks like we don't reach the same point. I have to view your implementation before more discussions. Thank you again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants