Displacy vizualization for entity linking

[shigapov]

Displacy can vizualize the enitity recognizer. It would be nice to have vizualization for entity linking pipelines as well. So that the links to entities in a knowledge base are also shown.

[polm]

Thanks for the suggestion!

[shigapov]

Let's add those links using "manual" option in displacy.

In Rendering data manually there is an example:

ex = [{"text": "But Google is starting from behind.",
       "ents": [{"start": 4, "end": 10, "label": "ORG"}],
       "title": None}]
html = displacy.render(ex, style="ent", manual=True)

I propose to add two more keys to "ents" ("kb_id" and "kb_url"):

ex = [{"text": "But Google is starting from behind.",
       "ents": [{"start": 4, "end": 10, "label": "ORG", "kb_id": "Q95", "kb_url": "https://www.wikidata.org/wiki/Q95"}],
       "title": None}]
html = displacy.render(ex, style="ent", manual=True)

Then in templates.py we need to add one more line to "TPL_ENT":

TPL_ENT = """
<mark class="entity" style="background: {bg}; padding: 0.45em 0.6em; margin: 0 0.25em; line-height: 1; border-radius: 0.35em;">
    {text}
    <span style="font-size: 0.8em; font-weight: bold; line-height: 1; border-radius: 0.35em; vertical-align: middle; margin-left: 0.5rem">{label}</span>
    <a style="text-decoration: none; color: black; font-weight: bold" href="{kb_url}">{kb_id}</a>
</mark>
"""

And in render.py we need to add two more lines (to specify kb_url and kb_id) and replace ent_settings = {"label": label, "text": entity, "bg": color}:

kb_id = str(span.get("kb_id") or "")
kb_url = str(span.get("kb_url") or "")
ent_settings = {"label": label, "text": entity, "bg": color, "kb_id": kb_id, "kb_url": kb_url}

If that's fine, I could make PR.

[shigapov]

Then it looks like

with clickable links to entities.

[polm]

That looks good to me. If you go ahead and open a PR someone more familiar with the related bits of code can review it.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.