Anaphora resolution - Revision history

Francis Tyers: Redirected page to Anaphora resolution module

2020-06-14T17:55:03Z

Redirected page to Anaphora resolution module

ScoopGracie at 03:01, 1 January 2020

2020-01-01T03:01:34Z

Francis Tyers: /* Integration with the pipeline */

2019-03-04T22:06:49Z

Integration with the pipeline

Francis Tyers: /* Machine learning component */

2017-12-01T15:41:46Z

Machine learning component

Francis Tyers: /* Ideas */

2017-12-01T15:39:45Z

Ideas

Francis Tyers: /* Biltrans gets extra LU */

2017-09-15T10:34:39Z

Biltrans gets extra LU

Francis Tyers: /* Biltrans gets extra LU */

2017-09-14T12:16:25Z

Biltrans gets extra LU

Francis Tyers at 12:10, 14 September 2017

2017-09-14T12:10:26Z

Francis Tyers at 12:06, 14 September 2017

2017-09-14T12:06:31Z

Francis Tyers at 09:35, 14 September 2017

2017-09-14T09:35:25Z

@@ Line 1: / Line 1: @@
+#redirect[[Anaphora resolution module]]
-{{TOCD}}
-Apertium has a problem with [[anaphora resolution]].
-For example:
-# If you have "el seu" in Catalan and are translating to French it could be "son" (third-person singular) or "leur" (third-person plural). If you are translating to English or Russian then you also need to know the gender of the possessor (его, ее, их).
-# If you are generating subject pronouns for a language, often you need to know the gender of the pronoun, e.g. "ha arribat" could be "He has arrived" or "She has arrived". In this case the "frequent" thing to do is to use the masculine pronoun, but that just relies on the male pronouns are used more frequently (see below):
-Usually this kind of thing is done over parse trees, but Apertium doesn't have parse trees, so we'd need to find another way to do it.
-Masculine and feminine subject pronouns in English wikipedia:
-<pre>
-5682787  he
-3469648  He
-1508156  she
-She
-</pre>
-== Ideas ==
-=== Integration with the pipeline ===
-One idea is to allow an extra LU to be passed into transfer using the following biltrans format:
-* Els grups del Parlament han mostrat aquest dimarts el seu suport al batle d'Alaró, Guillem Balboa, que va denunciar que uns desconeguts havien llançat un xai mort al pati de casa seva.
-Current output of biltrans:
-<pre>
-^El<det><def><m><pl>/The<det><def><m><pl>$ ^grup<n><m><pl>/group<n><pl>$ ^de<pr>/of<pr>/from<pr>$
-^el<det><def><m><sg>/the<det><def><m><sg>$ ^Parlament<n><m><sg>/Parliament<n><sg>$
-^haver<vbhaver><pri><p3><pl>/have<vbhaver><pri><p3><pl>$
-^mostrar<vblex><pp><m><sg>/show<vblex><pp><m><sg>/display<vblex><pp><m><sg>$
-^aquest<det><dem><m><sg>/this<det><dem><m><sg>$ ^dimarts<n><m><sp>/Tuesday<n><ND>$
-^el seu<det><pos><m><sg>/his<det><pos><m><sg>$ ^suport<n><m><sg>/support<n><sg>$
-^a<pr>/at<pr>/in<pr>/to<pr>$ ^el<det><def><m><sg>/the<det><def><m><sg>$
-^*batle/*batle$ ^de<pr>/of<pr>/from<pr>$ ^*Alaró/*Alaró$^.<sent>/.<sent>$
-</pre>
-Proposed output:
-<pre>
-^El<det><def><m><pl>/The<det><def><m><pl>/$ ^grup<n><m><pl>/group<n><pl>/$ ^de<pr>/of<pr>/from<pr>/$
-^el<det><def><m><sg>/the<det><def><m><sg>/$ ^Parlament<n><m><sg>/Parliament<n><sg>/$
-^haver<vbhaver><pri><p3><pl>/have<vbhaver><pri><p3><pl>/$
-^mostrar<vblex><pp><m><sg>/show<vblex><pp><m><sg>/display<vblex><pp><m><sg>/$
-^aquest<det><dem><m><sg>/this<det><dem><m><sg>/$ ^dimarts<n><m><sp>/Tuesday<n><ND>/$
-^el seu<det><pos><m><sg>/his<det><pos><m><sg>/group<n><pl>$ ^suport<n><m><sg>/support<n><sg>/$
-^a<pr>/at<pr>/in<pr>/to<pr>/$ ^el<det><def><m><sg>/the<det><def><m><sg>/$
-^*batle/*batle/$ ^de<pr>/of<pr>/from<pr>/$ ^*Alaró/*Alaró/$^.<sent>/.<sent>/$
-</pre>
-Note that an extra <tt>/</tt> has been added, after this <tt>/</tt> comes the "extra information", which could
-be the anaphoric referent. For example, at the moment the translation is:
-<pre>
-The groups of the Parliament have shown this Tuesday his support at the *batle of *Alaró...
-</pre>
-But if we add the information about referent:
-<pre>
-^el seu<det><pos><m><sg>/his<det><pos><m><sg>/grup<n><m><pl>$
-</pre>
-We could get "their" instead of "his". This extra information could be addressed in transfer using something like:
-<pre>
-<clip pos="1" side="ref" part="a_gen"/>
-<clip pos="1" side="ref" part="a_nbr"/>
-</pre>
-This would provide minimal disturbance to the existing transfer syntax:
-<pre>
-<choose>
-  <when>
-    <test><equal><clip pos="1" side="ref" part="a_nbr"/><lit-tag v="pl"/></equal></test>
-    <let><clip pos="1" side="tl" part="lem"/><lit v="their"/></let></when>
-  <when> <!-- Should also check for animacy: el cotxe ... el seu ... → the car ... its ...  -->
-    <test><and><equal><clip pos="1" side="ref" part="a_gen"/><lit-tag v="m"/></equal></test>
-    <let><clip pos="1" side="tl" part="lem"/><lit v="his"/></let></when>
-  <when> <!-- Should also check for animacy: la máquina ... el seu ... → the machine ... its ... -->
-    <test><equal><clip pos="1" side="ref" part="a_gen"/><lit-tag v="f"/></equal></test>
-    <let><clip pos="1" side="tl" part="lem"/><lit v="her"/></let></when>
-</choose>
-</pre>
-The actual information could be added either using CG or by developing another tool (e.g. using some kind of machine learning).
-=== Processing and learning component ===
-We'd first need a way to mark possible NPs as antecedents. We could use a transfer-pattern-like file format for this, where we have e.g.
-<pre>
-<def-cat n="det">
-  <cat-item tags="det.*"/>
-</def-cat>
-<def-cat n="adj">
-  <cat-item tags="adj.*"/>
-</def-cat>
-<def-cat n="nom">
-  <cat-item tags="n.*"/>
-</def-cat>
-...
-<markable>
-<pattern>
-  <pattern-item n="det"/>
-  <pattern-item n="adj"/>
-  <pattern-item n="nom" head/>
-</pattern>
-</markable>
-</pre>
-This would then match the sequence and store the "nom" (and it's position) as the head and a potential antecedent.
-==Further reading==
-* Ruslan Mitkov (1999) "Multilingual Anaphora Resolution". ''Machine Translation. Volume 14, Issue 3–4, pp 281–299
-[[Category:Development]]

@@ Line 4: / Line 4: @@
 For example:
-# If you have "el seu" in Catalan and are translating to French it could be "son" (third-person singular or "leur" (third-person plural). If you are translating to English or Russian then you also need to know the gender of the possessor (его, ее, их).
+# If you have "el seu" in Catalan and are translating to French it could be "son" (third-person singular) or "leur" (third-person plural). If you are translating to English or Russian then you also need to know the gender of the possessor (его, ее, их).
 # If you are generating subject pronouns for a language, often you need to know the gender of the pronoun, e.g. "ha arribat" could be "He has arrived" or "She has arrived". In this case the "frequent" thing to do is to use the masculine pronoun, but that just relies on the male pronouns are used more frequently (see below):

@@ Line 41: / Line 41: @@
 <pre>
-^El<det><def><m><pl>/The<det><def><m><pl>/$ ^grup<n><m><pl>/group<n><pl>$ ^de<pr>/of<pr>/from<pr>/$
+^El<det><def><m><pl>/The<det><def><m><pl>/$ ^grup<n><m><pl>/group<n><pl>/$ ^de<pr>/of<pr>/from<pr>/$
 ^el<det><def><m><sg>/the<det><def><m><sg>/$ ^Parlament<n><m><sg>/Parliament<n><sg>/$
 ^haver<vbhaver><pri><p3><pl>/have<vbhaver><pri><p3><pl>/$

@@ Line 88: / Line 88: @@
 The actual information could be added either using CG or by developing another tool (e.g. using some kind of machine learning).
-=== Machine learning component ===
+=== Processing and learning component ===
 We'd first need a way to mark possible NPs as antecedents. We could use a transfer-pattern-like file format for this, where we have e.g.

@@ Line 19: / Line 19: @@
 == Ideas ==
-=== Biltrans gets extra LU ===
+=== Integration with the pipeline ===
 One idea is to allow an extra LU to be passed into transfer using the following biltrans format:
@@ Line 87: / Line 87: @@
 The actual information could be added either using CG or by developing another tool (e.g. using some kind of machine learning).
+=== Machine learning component ===
+We'd first need a way to mark possible NPs as antecedents. We could use a transfer-pattern-like file format for this, where we have e.g.
+<pre>
+<def-cat n="det">
+  <cat-item tags="det.*"/>
+</def-cat>
+<def-cat n="adj">
+  <cat-item tags="adj.*"/>
+</def-cat>
+<def-cat n="nom">
+  <cat-item tags="n.*"/>
+</def-cat>
+...
+<markable>
+<pattern>
+  <pattern-item n="det"/>
+  <pattern-item n="adj"/>
+  <pattern-item n="nom" head/>
+</pattern>
+</markable>
+</pre>
+This would then match the sequence and store the "nom" (and it's position) as the head and a potential antecedent.
 ==Further reading==

← Older revision		Revision as of 12:10, 14 September 2017
Line 1:		Line 1:
			{{TOCD}}
	Apertium has a problem with [[anaphora resolution]].		Apertium has a problem with [[anaphora resolution]].