Entity Linking in Tweets
Named entity recognition and entity linking in tweets: annotators identify entity mentions in short, noisy social-media text and map each mention to its corresponding knowledge base entry. A generic showcase design for social-media entity linking and knowledge base population.
Configuration Fileconfig.yaml
# Entity Linking in Tweets
# A generic showcase design for social-media entity linking (no specific
# primary source). Annotators identify entity mentions in tweets and map
# each to its knowledge base entry.
#
# This task asks annotators to identify entity mentions in tweets and
# provide their corresponding knowledge base URIs (e.g., Wikipedia or
# Wikidata URLs). Entity mentions include persons, organizations,
# locations, events, and other named entities.
#
# Annotation Steps:
# 1. Highlight all entity mentions in the tweet text
# 2. For each entity, provide the corresponding knowledge base URI
annotation_task_name: "Entity Linking in Tweets"
task_dir: "."
data_files:
- sample-data.json
item_properties:
id_key: "id"
text_key: "text"
output_annotation_dir: "annotation_output/"
output_annotation_format: "json"
port: 8000
server_name: localhost
annotation_schemes:
- annotation_type: span
name: entity_mentions
description: "Highlight all named entity mentions in the tweet"
labels:
- "Entity Mention"
- annotation_type: text
name: entity_uri
description: "Provide the knowledge base URI (e.g., Wikipedia URL) for each identified entity"
annotation_instructions: |
You will see a tweet that may contain named entities (people, organizations, places, events, etc.).
1. Highlight all named entity mentions in the text using the span annotation tool.
2. For each entity, provide its corresponding knowledge base URI (Wikipedia or Wikidata URL).
3. If multiple entities are present, list all URIs separated by semicolons.
Note: Focus on proper nouns and named entities, not common nouns.
html_layout: |
<div style="padding: 15px; max-width: 800px; margin: auto;">
<div style="background: #f0f9ff; border: 1px solid #bae6fd; border-radius: 8px; padding: 16px; margin-bottom: 16px;">
<strong style="color: #0369a1;">Tweet:</strong>
<p style="font-size: 16px; line-height: 1.7; margin: 8px 0 0 0;">{{text}}</p>
</div>
</div>
allow_all_users: true
instances_per_annotator: 50
annotation_per_instance: 2
allow_skip: true
skip_reason_required: false
Sample Datasample-data.json
[
{
"id": "entity_link_001",
"text": "Just watched Oppenheimer at the IMAX theater in Manhattan. Christopher Nolan really outdid himself with this one. Cillian Murphy deserves every award."
},
{
"id": "entity_link_002",
"text": "The Lakers are playing the Celtics at Staples Center tonight. LeBron James vs Jayson Tatum is going to be epic!"
}
]
// ... and 8 more itemsGet This Design
Clone or download from the repository
Quick start:
git clone https://github.com/davidjurgens/potato-showcase.git cd potato-showcase/text/entity-linking/entity-linking-tweets potato start config.yaml
Details
Annotation Types
Domain
Use Cases
Tags
Found an issue or want to improve this design?
Open an IssueRelated Designs
Check-COVID: Fact-Checking COVID-19 News Claims
Fact-checking COVID-19 news claims. Annotators verify claims against evidence, identify supporting/refuting spans, and provide verdicts with explanations. Based on the Check-COVID dataset targeting misinformation during the pandemic.
Clickbait Spoiling
Classification and extraction of spoilers for clickbait posts, including spoiler type identification and span-level spoiler detection. Based on SemEval-2023 Task 5 (Fröbe et al.).
CrossRE: Cross-Domain Relation Extraction
Cross-domain relation extraction across 6 domains (news, politics, science, music, literature, AI). Annotators identify entities and label 17 relation types between entity pairs, enabling study of domain transfer in relation extraction.