ONTOSIGN / ASL Knowledge Explorer is a multimodal Linguistic Linked Open Data (LLOD) framework for exploring American Sign Language (ASL) through natural-language queries. It represents lexical, semantic, phonological, psycholinguistic, and multimodal sign-language information as an OntoLex-Lemon RDF knowledge graph and provides LLM-powered natural-language-to-SPARQL querying.
π Try ONTOSIGN Live β Explore the ASL knowledge graph through natural-language queries and inspect the generated SPARQL.
Team: Fashad Ahmed Siddique Β· Zunaira Hasnain Β· Oreoluwa Babatunde Β· Luana Nova Β· Nuveyba Ekinci
Project: Building a Multimodal Linked Data Framework for Sign Language Lexicons
Event: 6th Summer Datathon on Linguistic Linked Open Data (SD-LLOD-26)
ASL Knowledge Explorer demonstrates how sign-language dictionaries and lexical resources can be transformed into multimodal Linguistic Linked Open Data and explored without requiring users to know SPARQL.
The application follows the pipeline:
Natural Language β NL-to-SPARQL β Knowledge Graph β Linked Results
Users can ask questions such as:
Show me Food signsWhich one-handed signs are articulated at the head?Which signs share the lemma wrong?Show Animal signs articulated at the head and their handshapesWhich signs do not have a path movement?Show signs with frequency at least 5
The current pilot contains 50 curated ASL signs and integrates lexical, semantic, phonological, psycholinguistic, and multimodal information.
The ASL data is represented as an RDF knowledge graph using OntoLex-Lemon, SKOS, and related Semantic Web vocabularies. Lexical entries are connected to canonical forms, concepts, semantic fields, phonological properties, psycholinguistic measures, and multimedia references.
Visualization of a portion of the ASL Knowledge Explorer RDF knowledge graph.
The graph supports relationships across several linguistic dimensions:
- Lexical: lexical entries, lemmas, translations, lexical class
- Semantic: concepts and semantic fields
- Phonological: sign type, handshape, selected fingers, thumb position, movement, location, and contact
- Psycholinguistic: frequency, iconicity, phonological complexity, and neighborhood density
- Multimodal: handshape images and external ASL-LEX visualization references
- Natural-language querying of an ASL knowledge graph
- Schema-grounded NL β SPARQL generation
- GPT-OSS-20B via Groq for LLM-based query generation
- Read-only SPARQL validation before execution
- RDF modeling based on OntoLex-Lemon
- Semantic and lexical retrieval
- Phonological querying across handshape, movement, location, contact, and sign type
- Psycholinguistic querying using frequency, iconicity, complexity, and neighborhood density
- Multimodal references to handshape images and ASL-LEX visualization pages
- Optional execution against a live SPARQL endpoint
- Local querying over the curated real 50-sign dataset when an endpoint is not configured
- Generated SPARQL viewer for transparency and debugging
- Linked result cards for matching ASL signs
- Next.js 15
- React 19
- TypeScript
- Groq SDK
- GPT-OSS-20B
- RDF / Turtle
- SPARQL
- OntoLex-Lemon
- SKOS
- Linguistic Linked Open Data (LLOD)
- GraphDB / SPARQL-compatible RDF stores
Datathon/
βββ app/
β βββ api/
β β βββ ask/
β β βββ route.ts
β βββ globals.css
β βββ layout.tsx
β βββ page.tsx
β
βββ components/
β βββ ResultCard.tsx
β βββ SearchBox.tsx
β βββ SparqlViewer.tsx
β
βββ data/
β βββ ASLLEX_dataset_50.csv
β βββ asllex_50_revised_ontolex_model.ttl
β βββ asllex_50_revised_queries.sparql
β
βββ lib/
β βββ kg-schema.ts
β βββ nl-to-sparql.ts
β βββ query-real-data.ts
β βββ real-data.ts
β βββ sparql-endpoint.ts
β βββ types.ts
β βββ validate-sparql.ts
β
βββ Resources/
β βββ KG.jpeg
β βββ SIGN LANGUAGE MODELLING & LINKING GROUP.pdf
β
βββ .env.example
βββ .gitignore
βββ README.md
βββ package.json
βββ package-lock.json
βββ tsconfig.json
The repository includes a curated 50-sign ASL pilot dataset, its RDF/Turtle representation, and competency SPARQL queries.
| File | Description |
|---|---|
data/ASLLEX_dataset_50.csv |
Curated 50-sign pilot dataset |
data/asllex_50_revised_ontolex_model.ttl |
RDF/Turtle knowledge graph modeled with OntoLex-Lemon |
data/asllex_50_revised_queries.sparql |
Example and competency SPARQL queries |
The model represents information including:
- Entry and lemma identifiers
- Dominant and nondominant translations
- Lexical class
- Semantic field
- Sign type
- Handshape
- Selected fingers
- Thumb position
- Path movement
- Repeated movement
- Major and minor location
- Contact
- Frequency
- Iconicity
- Phonological complexity
- Neighborhood density
- Multimedia references
Semantic and phonological categories are represented as reusable RDF resources rather than only as flat string values.
User Question
β
βΌ
Next.js Interface
β
βΌ
POST /api/ask
β
βΌ
Schema-Grounded NL β SPARQL
β
βΌ
Read-Only SPARQL Validation
β
βββββ SPARQL_ENDPOINT_URL configured βββββΊ RDF Knowledge Graph
β β
β βΌ
β Results
β
βββββ No endpoint ββββββββββββββββββββββββΊ Local 50-Sign Dataset
β
βΌ
Results
The application supports three configurations:
- Local dataset mode β uses the supplied real 50-sign dataset with the schema-aware fallback query generator.
- LLM + local dataset β GPT-OSS generates SPARQL while matching result cards are retrieved from the local 50-sign dataset.
- LLM + live RDF knowledge graph β generated SPARQL is validated and executed directly against a configured RDF/SPARQL endpoint.
The language model is not asked to generate arbitrary SPARQL. Generation is grounded in the actual knowledge-graph schema defined in:
lib/kg-schema.ts
The prompt and few-shot examples are implemented in:
lib/nl-to-sparql.ts
They cover query families including:
- Semantic retrieval
- Phonological retrieval
- Combined semantic + phonological constraints
- Lemma lookup
- Translation lookup
- Missing-property queries
- Numerical thresholds
- Psycholinguistic constraints
- Neighborhood analysis
- Multimodal retrieval
Before execution, generated SPARQL is checked by:
lib/validate-sparql.ts
Natural-language question:
Which one-handed signs are articulated at the head?
Example generated query:
PREFIX ontolex: <http://www.w3.org/ns/lemon/ontolex#>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX dct: <http://purl.org/dc/terms/>
PREFIX aslkg: <https://w3id.org/asl-lex-kg/ontology#>
SELECT ?entry ?entryId
WHERE {
?entry a aslkg:SignLexicalEntry ;
dct:identifier ?entryId ;
ontolex:lexicalForm ?form .
?form aslkg:signType ?signTypeResource ;
aslkg:majorLocation ?locationResource .
?signTypeResource skos:prefLabel "One Handed"@en .
?locationResource skos:prefLabel "Head"@en .
}
ORDER BY ?entryIdThe matching ASL signs are returned to the interface and displayed as result cards.
- Node.js 18+ (current LTS recommended)
- npm
npm installnpm run devThen open:
http://localhost:3000
The application can run using the supplied local dataset without requiring an API key.
Create .env.local from the example environment file.
On macOS/Linux:
cp .env.example .env.localOn Windows PowerShell:
Copy-Item .env.example .env.localAdd your Groq API key:
GROQ_API_KEY=your_groq_api_keyRestart the development server.
When configured, the application uses openai/gpt-oss-20b through Groq for natural-language-to-SPARQL generation.
Never commit
.env.localor expose API credentials publicly.
To execute generated SPARQL directly against the RDF knowledge graph, load:
data/asllex_50_revised_ontolex_model.ttl
into a SPARQL-compatible RDF store such as GraphDB or Apache Jena Fuseki.
Then add the query endpoint to .env.local:
SPARQL_ENDPOINT_URL=your_sparql_query_endpointA complete configuration can look like:
GROQ_API_KEY=your_groq_api_key
SPARQL_ENDPOINT_URL=your_sparql_query_endpointWhen SPARQL_ENDPOINT_URL is configured, generated SPARQL is executed directly against the live RDF knowledge graph.
Example request:
{
"question": "Show me Food signs"
}The response includes:
- Original natural-language question
- Generated SPARQL
- Number of matching signs
- Matching result records
- Current execution mode
- Execution note
A central goal of the project is to move beyond a conventional lexical table by representing multiple dimensions of sign-language information as linked data.
Lexical Information
β
Semantic Concepts
β
Phonological Form
β
Psycholinguistic Measures
β
Multimedia References
This enables cross-dimensional queries such as retrieving signs from a semantic category while simultaneously filtering by articulation location, handshape, movement, contact, frequency, or iconicity.
ASL Knowledge Explorer was developed during the 6th Summer Datathon on Linguistic Linked Open Data (SD-LLOD-26), held from August 30 to September 4, 2026 at Villa Cagnola, Gazzada Schianno, Italy.
The datathon brings together researchers and students working with Linguistic Linked Open Data, Semantic Web technologies, natural language processing, and linguistic data science.
- Zunaira Hasnain
- Luana Nova
- Nuveyba Ekinci
- Fashad Ahmed Siddique
- Oreoluwa Babatunde
- Jorge Gracia del RΓo
- Christian Chiarcos
- Blerina Spahiu
The pilot dataset is derived from ASL-LEX resources and is used for research and datathon prototyping.
Multimedia references are represented as external references rather than redistributed ASL-LEX videos. Users of this repository should consult the original ASL-LEX resource and its licensing and usage conditions before redistributing source data or multimedia material.
- Scale beyond the 50-sign pilot
- Link additional sign-language lexical resources
- Add richer multimedia annotations
- Link to external multilingual lexical and conceptual resources
- Deploy a public SPARQL endpoint
- Evaluate NL-to-SPARQL accuracy systematically
- Improve complex cross-modal linguistic querying
- Extend the framework to additional sign languages
We thank the organizers and mentors of the 6th Summer Datathon on Linguistic Linked Open Data (SD-LLOD-26) for their guidance and support during the development of this project.
npm run build
npm startASL Knowledge Explorer Β· OntoLex-Lemon Β· RDF Β· SPARQL Β· LLOD Β· Multimodal Sign Language Data
