Metadata-Version: 2.4
Name: lion_linker
Version: 0.1.0
Summary: A package for entity linking using LionLinker.
Author-email: Roberto Avogadro <roberto.avogadro@sintef.no>
License: MIT
Project-URL: Homepage, https://github.com/roby-avo/lion_linker
Classifier: Programming Language :: Python :: 3
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: OS Independent
Requires-Python: >=3.10
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: pandas==2.2.3
Requires-Dist: requests==2.32.4
Requires-Dist: ollama==0.3.3
Requires-Dist: aiohttp==3.12.14
Requires-Dist: asyncio==3.4.3
Requires-Dist: tqdm==4.67.0
Requires-Dist: openai==1.54.4
Requires-Dist: python-dotenv==1.0.1
Requires-Dist: jsonargparse==4.37.0
Requires-Dist: torch>=2.8.0
Requires-Dist: transformers>=4.34.0
Provides-Extra: app
Requires-Dist: fastapi==0.115; extra == "app"
Requires-Dist: pydantic<3; extra == "app"
Requires-Dist: uvicorn==0.34; extra == "app"
Requires-Dist: pydantic-settings<3,>=2.0; extra == "app"
Requires-Dist: motor<4,>=3.5; extra == "app"
Provides-Extra: dev
Requires-Dist: flake8; extra == "dev"
Requires-Dist: black; extra == "dev"
Requires-Dist: isort; extra == "dev"
Requires-Dist: mypy; extra == "dev"
Requires-Dist: pre-commit; extra == "dev"
Provides-Extra: tablellama
Requires-Dist: transformers==4.34; extra == "tablellama"
Requires-Dist: tokenizers==0.14; extra == "tablellama"
Requires-Dist: protobuf==6.32.0; extra == "tablellama"
Requires-Dist: sentencepiece==0.2.1; extra == "tablellama"
Dynamic: license-file

# lion_linker

**lion_linker** is a Python library that uses Large Language Models (LLMs) to perform entity linking over tabular data. It efficiently links entity mentions in tables to relevant knowledge graph entities using customizable prompts and batch processing.

<img src="logo/logo.webp" alt="lion_linker Logo" width="200"/>

## Overview

**lion_linker** simplifies the process of entity linking by leveraging LLMs to identify and connect textual data in tables to relevant entities in a knowledge base. It is highly customizable, making it ideal for projects involving research, NLP, and large-scale data processing.

## Features

- **Entity Linking with LLMs**: Provides accurate and context-aware entity linking using large language models.
- **Command Line Interface (CLI)**: Process CSV files via the command line for ease of use and automation.
- **Customizable Prompt Templates**: Adjust the linking prompt to fit your data structure.
- **Scalable for Large Datasets**: Process large datasets by batching the work and customizing API result limits.
- **Flexible API**: Programmatic interface for advanced users.
- **REST API (FastAPI)**: Host LionLinker as a background job service with queued workloads.

## Installation

To use **lion_linker**, you will need to install both the Python package and **Ollama**, which must be running locally.

### Step 1: Install **lion_linker** via pip

You can install the latest version directly from the GitHub repository using the following command:

```bash
pip install git+https://github.com/enRichMyData/lion_linker.git
```

Alternatively, clone the repository and install from source:

```bash
git clone https://github.com/enRichMyData/lion_linker.git
cd lion_linker
pip install -e .
```

To use [TableLlama](https://osu-nlp-group.github.io/TableLlama/) run the following:

```bash
pip install git+https://github.com/enrichMyData/lion_linker.git#egg=lion_linker[tablellama]
pip install -U huggingface-hub
```

### Step 2: Install **Ollama**

**Ollama** is required for the large language models to function with **lion_linker**. You must install it separately and ensure it is running locally.

1. Download and install **Ollama** from [Ollama's official website](https://ollama.com/download).
2. After installation, start the **Ollama** service locally by running the following command:

```bash
ollama serve
```

This ensures that the LLM models can be accessed by **lion_linker** during the entity linking process.

### Step 3:
lion_linker requires certain environment variables to be set, such as the API_URL and API_TOKEN for the entity retrieval API. To make this process easier, a .env.template file is provided in the repository.

1.	Create a .env file by copying .env.template:
```bash
cp .env.template .env
```

2.	Edit the .env file to add your specific API details. Open .env in a text editor and fill in the required values:
```bash
RETRIEVER_ENDPOINT=https://lamapi.hel.sintef.cloud/lookup/entity-retrieval
RETRIEVER_TOKEN=your_api_token  # Replace with your actual API token
```
The .env file will be used to securely store your Retriever credentials and other sensitive configuration data, so make sure it is not committed to version control. Moreover, if one wants to use [OpenRouter](https://openrouter.ai/) the following additional credential must be set:
```bash
OPENAI_API_KEY=sk-v1-...
```
which can be retreived from the [OpenRouter settings](https://openrouter.ai/settings/keys).

3.	Verify the .env file by checking that RETRIEVER_ENDPOINT and RETRIEVER_TOKEN are correctly set, as these values will be automatically loaded by lion_linker when it runs.

## Usage

### Python Example

```python
import os
import subprocess

from dotenv import load_dotenv

from lion_linker.lion_linker import LionLinker
from lion_linker.retrievers import LamapiClient

# Load environment variables from the .env file
load_dotenv()

# Define necessary file paths and parameters
input_csv = "tests/data/film.csv"
prompt_file_path = "lion_linker/prompt/prompt_template.txt"
model_name = "gemma2:2b"  # Use the correct model name
output_csv = "output_test.csv"
chunk_size = 16  # How many rows to process
num_candidates = 20  # Maximum number of candidates from the Retriever per mention
format_candidates = True  # Format candidates as in TableLlama prompt
table_ctx_size = 1

# Load API parameters from environment variables
retriever_endpoint = os.getenv("RETRIEVER_ENDPOINT")
retriever_token = os.getenv("RETRIEVER_TOKEN")

# Additional parameters as per the latest LionLinker version
mention_columns = ["title"]  # Columns to link entities from
compact_candidates = True  # Whether to compact candidates list
model_api_provider = "ollama"  # Optional model API provider
ollama_host = "http://localhost:11434"  # Default Ollama host if not specified it will use the Default Ollama host anyway
model_api_key = None  # Optional model API key if required
gt_columns = []  # Specify any ground truth columns to exclude for testing

# Initialize the retriever instance
retriever = LamapiClient(retriever_endpoint, retriever_token, num_candidates=num_candidates)

# Initialize the LionLinker instance
lion_linker = LionLinker(
    input_csv=input_csv,
    model_name=model_name,
    retriever=retriever,
    output_csv=output_csv,
    prompt_file_path=prompt_file_path,
    chunk_size=chunk_size,
    mention_columns=mention_columns,
    compact_candidates=compact_candidates,
    model_api_provider=model_api_provider,
    ollama_host=ollama_host,
    model_api_key=model_api_key,
    gt_columns=gt_columns,
    table_ctx_size=table_ctx_size,
    format_candidates=format_candidates,
)

# Start the Ollama server as a background process
process = subprocess.Popen(["ollama", "serve"])

# Run the entity linking
await lion_linker.run()

# Stop the Ollama server
process.terminate()
```

### CLI Example

```bash
python -m lion_linker.cli \
  --lion.input_csv "./data/film.csv" \
  --lion.model_name "gemma2:2b" \
  --lion.mention_columns '[title]' \
  --lion.ollama_host "http://localhost:11434" \
  --lion.format_candidates True \
  --retriever.class_path lion_linker.retrievers.LamapiClient \
  --retriever.endpoint "https://lamapi.hel.sintef.cloud/lookup/entity-retrieval" \
  --retriever.token "lamapi_demo_2023" \
  --retriever.kg wikidata \
  --retriever.num_candidates 5 \
  --retriever.cache False
```

If one wants to change the retriever and for example use the Wikidata Lookup Service instead, the following can be used instead:

```bash
python -m lion_linker.cli \
  --lion.input_csv "./data/film.csv" \
  --lion.model_name "gemma2:2b" \
  --lion.mention_columns '[title]' \
  --lion.ollama_host "http://localhost:11434" \
  --lion.format_candidates True \
  --retriever.class_path lion_linker.retrievers.WikidataClient \
  --retriever.endpoint "https://query.wikidata.org/sparql" \
  --retriever.language "en" \
  --retriever.num_candidates 5
```

Another possibility is to retrieve candidates for mentions through [OpenRefine](https://openrefine.org/):

```bash
python -m lion_linker.cli \
  --lion.input_csv "./data/film.csv" \
  --lion.model_name "gemma2:2b" \
  --lion.mention_columns '[title]' \
  --lion.ollama_host "http://localhost:11434" \
  --lion.format_candidates True \
  --retriever.class_path lion_linker.retrievers.OpenRefineClient \
  --retriever.endpoint "https://wikidata.reconci.link/api" \
  --retriever.num_candidates 5
```

### Explanation of Parameters

- `input_csv`: Path to your input CSV file.
- `output_csv`: Path where the output file will be saved.
- `ollama_host`: The host where the Ollama service is running.
- `--prompt_file_path`: Path to a file containing a custom prompt template.

- `--model`: The LLM model to use for entity linking.
- `--chunk_size`: Defines how many rows to process at once.
- `--mention_columns`: Columns in the CSV that contain entity mentions.
- `--num_candidates`: Maximum number of candidates returned by the API per mention.

## REST API server

The repository now includes a FastAPI application (located in `app/`) that exposes a small REST interface for working with LionLinker jobs. The service persists all datasets, tables, and job metadata in MongoDB, so you get durability and a multi-process friendly queue without managing local JSON files.

### Install dependencies

```bash
pip install -e .[app]
```

### Configure

The API shares the same environment variables as the Python/CLI interfaces. The most relevant flags are:

- `RETRIEVER_ENDPOINT`, `RETRIEVER_TOKEN`: LamAPI (or compatible) endpoint configuration.
- LionLinker-specific settings (model, prompts, mention columns, etc.) should be supplied per request via `lionConfig` / `retrieverConfig` in the payload.
- `LION_DRY_RUN=true`: force offline/dry runs that emit `ANSWER:NIL` predictions without contacting retrievers or models (handy for local testing).
- `MONGO_URI` (defaults to `mongodb://localhost:27017`), `MONGO_DB`, and `MONGO_COLLECTION_PREFIX`: connection settings for the MongoDB instance backing the job store.
- `WORKSPACE_PATH` (defaults to `data/api_runs`): where intermediate CSV/JSON artifacts are written inside the container.
- `PREDICTION_BATCH_ROWS`: controls the chunk size used when persisting prediction metadata and reporting `predictionBatches`.

### Run

```bash
uvicorn app.main:app --reload
```

Detailed API documentation is available in `docs/api_reference.md` and via the autogenerated Swagger UI at `/docs`.

### Docker Compose

You can spin up the API and a MongoDB instance together using the provided compose file:

```bash
cd docker/service
docker compose up --build
```

The compose stack exposes the API on `http://localhost:9000`, MongoDB on `mongodb://localhost:27017`, and mounts the host `data/` directory into the container at `/app/data` so persisted predictions (CSV, JSON, MongoDB volume) are easy to inspect.

### Endpoints

- `POST /dataset` – registers dataset/table payloads (you can send multiple at once). Returns dataset and table identifiers that can be reused later.
- `POST /annotate` – accepts the same payload as `/dataset` and enqueues a LionLinker job for each table. An optional `token` query parameter is stored with the job and checked when polling.
- `GET /dataset/{dataset_id}/table/{table_id}` – checks the most recent job for that table. Supports pagination via `page`/`per_page` and includes prediction results once the job completes.
- `GET /annotate/{job_id}` – fetches the state of a specific job (mirrors the information returned when polling via dataset/table).
  - Completed jobs now stream predictions directly from table rows stored in MongoDB; the API falls back to the legacy JSON files if a job predates the Mongo-backed persistence.

You can override LionLinker settings per request by attaching optional `lionConfig` and `retrieverConfig` objects to each table payload. For example:

```json
{
  "datasetName": "EMD-BC",
  "tableName": "SN-BC-1753173071015729",
  "header": ["Point of Interest", "Place"],
  "rows": [
    {"idRow": 1, "data": ["John F. Kennedy Presidential Library and Museum", "Columbia Point"]},
    {"idRow": 2, "data": ["Petrie Museum of Egyptian Archaeology", "London"]}
  ],
  "lionConfig": {
    "chunkSize": 16,
    "mentionColumns": ["Point of Interest"],
    "tableCtxSize": 2,
    "modelName": "gemma2:2b"
  },
  "retrieverConfig": {
    "numCandidates": 5,
    "endpoint": "https://lamapi.hel.sintef.cloud/lookup/entity-retrieval",
    "token": "lamapi_demo_2023"
  }
}
```

The overrides are stored with the job and surfaced via `GET /annotate/{job_id}`, so you can confirm which parameters were used.

Example request bodies (matching the payloads from the CLI):

```json
[
  {
    "datasetName": "EMD-BC",
    "tableName": "SN-BC-1753173071015729",
    "header": ["Point of Interest", "Place"],
    "rows": [
      {"idRow": 1, "data": ["John F. Kennedy Presidential Library and Museum", "Columbia Point"]}
    ],
    "retrieverConfig": {
      "kg": "wikidata"
    }
  }
]
```

Send this to `/annotate` to start processing. Poll `/dataset/{datasetId}/table/{tableId}` until the job reports `status: completed`.

### Example: annotate the demo film table with OpenRouter

The repository ships with `examples/send_film_annotation.py`, a ready-to-run helper that
reads `data/film.csv`, posts it to the API, and prints the annotated rows while using
OpenRouter as the LLM provider.

```bash
export OPENAI_API_KEY="sk-or-..."
python examples/send_film_annotation.py
```

Optional environment variables:

- `LION_LINKER_API_URL` (defaults to `http://localhost:9000`)
- `OPENROUTER_MODEL_NAME` (defaults to `anthropic/claude-3-haiku`)
- `ANNOTATION_TOKEN` to include a token query parameter
- `RETRIEVER_CONFIG_JSON` to provide a full JSON retriever configuration
- or populate individual fields such as `RETRIEVER_CLASS_PATH`, `RETRIEVER_ENDPOINT`,
  `RETRIEVER_TOKEN`, `RETRIEVER_NUM_CANDIDATES`, `RETRIEVER_CACHE`, and
  `RETRIEVER_EXTRA_JSON` for additional key/value pairs

The script depends on `requests`; install it with your preferred package manager (for
example `uv add requests` or `pip install requests`) if it is not already available.

## Running Tests

You can run the tests with:

```bash
python -m unittest discover -s tests
```

This will execute all unit tests in the `tests/` directory.

## License

This project is licensed under the Apache License - see the [LICENSE](LICENSE) file for details.
