Hi Ankur,
On 2/28/14, 2:00 AM, Ankur Padia wrote:
>Among the approach listed before, I will prefer TBSL as it scope is
> relatively wider.
All right, go ahead with that.
> Ideally QA engine for DBpedia should be able to handle all kinds of
> question with its appropriate semantic parsing
Dear Chirstina,
>
> Looks good!
>
Thank you for your valuable feedback.
> So which one do you prefer?
>
Among the approach listed before, I will prefer TBSL as it scope is
relatively wider.
> And what are the most crucial aspects for you, that play a role when
> deciding for one?
>
Dear Ankur,
Looks good! So which one do you prefer? And what are the most crucial
aspects for you, that play a role when deciding for one?
For me, one very important point, that you mention in your pro and con
lists, is the kind of queries an approach can handle. Should a QA engine
for DBped
Hello every one,
I have tried to list couple of advantages and disadvantages for the
approach [1, 2] and [3]. Please let me know if there are any correction.
Following is description of the systems [1, 2, 3] followed by its
respective advantages and disadvantages.
*TBSL [1] - Template bas
Hi Ankur,
Find my answers inline.
On 2/24/14, 8:08 PM, Ankur Padia wrote:
> Hello Marco,
>
> Please find answer to the question as mentioned below.
>
> 1. Have you already had a look at the code from the different options?
>
> Not yet, but have started with TBSL and had a doubt on would we b
