On 1/25/2013 12:16 PM, Filipe Araujo wrote:
Hi there,
<... SNIP ...>
As an example for this, right now i have:
<START:description> Senior Developer <END> <START:date> 2009-current <END>
<START:company> Apple Inc. <END>
What i hoped i could have:
<START:jobs>
<START:description> Senior Developer <END> <START:date> 2009-current
<END> <START:company> Apple Inc. <END>
...
<END>
Is a nested tag approach the correct way of trying to achieve this
correlation between entities or is there better approaches to this problem?
Thank you very much for your help.
Best regards,
No, the name finder models don't have support for nested tokens. Any
training data setup like this would produce problems and would not train.
Maybe another approach like:
<START:job_description> ... <END> <START:job_date> ... <END>
<START:job_date> ... <END>
<START:job_company> ... <END>
Then using an XML type generator to produce a more logical splitting
.... afterwards.
James
