From 1f672717ad184b179650e5566b9725bb4ecd66a8 Mon Sep 17 00:00:00 2001 From: Herbert Ullrich Date: Wed, 25 Feb 2026 17:55:38 +0100 Subject: [PATCH] Add Underline video and slides links for AVeriTeC and FEVER 8 --- .github/workflows/deploy.yml | 14 ++++---- README.md | 26 +++++++-------- package.json | 2 +- src/components/Header.astro | 11 +++++-- .../publications/aic-ctu-at-averimatec.md | 7 ++-- .../aic-ctu-fever-8-long-context-rag.md | 12 +++---- .../aic-ctu-system-at-averitec.md | 12 +++---- ...ssing-quality-of-information-extraction.md | 5 ++- .../claim-extraction-for-fact-checking.md | 5 ++- .../blog/publications/csfever-and-ctkfacts.md | 6 ++-- .../pipeline-and-dataset-generation.md | 6 ++-- src/pages/index.astro | 2 +- src/pages/posts/[...page].astro | 5 ++- src/pages/publications/index.astro | 32 +++++++++++-------- 14 files changed, 74 insertions(+), 71 deletions(-) diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index 196d6bb..208213a 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -4,7 +4,7 @@ on: # Trigger the workflow every time you push to the `main` branch # Using a different branch name? Replace `main` with your branch’s name push: - branches: [ main ] + branches: [main] # Allows you to run this workflow manually from the Actions tab on GitHub. workflow_dispatch: @@ -23,12 +23,12 @@ jobs: - name: Install, build, and upload your site uses: withastro/action@v5 # with: - # path: . # The root location of your Astro project inside the repository. (optional) - # node-version: 24 # The specific version of Node that should be used to build your site. Defaults to 22. (optional) - # package-manager: pnpm@latest # The Node package manager that should be used to install dependencies and build your site. Automatically detected based on your lockfile. (optional) - # build-cmd: pnpm run build # The command to run to build your site. Runs the package build script/task by default. (optional) + # path: . # The root location of your Astro project inside the repository. (optional) + # node-version: 24 # The specific version of Node that should be used to build your site. Defaults to 22. (optional) + # package-manager: pnpm@latest # The Node package manager that should be used to install dependencies and build your site. Automatically detected based on your lockfile. (optional) + # build-cmd: pnpm run build # The command to run to build your site. Runs the package build script/task by default. (optional) # env: - # PUBLIC_POKEAPI: 'https://pokeapi.co/api/v2' # Use single quotation marks for the variable value. (optional) + # PUBLIC_POKEAPI: 'https://pokeapi.co/api/v2' # Use single quotation marks for the variable value. (optional) deploy: needs: build @@ -39,4 +39,4 @@ jobs: steps: - name: Deploy to GitHub Pages id: deployment - uses: actions/deploy-pages@v4 \ No newline at end of file + uses: actions/deploy-pages@v4 diff --git a/README.md b/README.md index 916326f..25867e9 100644 --- a/README.md +++ b/README.md @@ -150,20 +150,20 @@ All commands are run from the root of the project, from a terminal: > **_Note!_** For `Docker` commands we must have it [installed](https://docs.docker.com/engine/install/) in your machine. -| Command | Action | -| :----------------------------------- | :------------------------------------------------------------------------------------------------------------------------------- | -| `pnpm install` | Installs dependencies | -| `pnpm run dev` | Starts local dev server at `localhost:4321` | -| `pnpm run build` | Build your production site to `./dist/` | -| `pnpm run preview` | Preview your build locally, before deploying | -| `pnpm run format:check` | Check code format with Prettier | -| `pnpm run format` | Format codes with Prettier | -| `pnpm run sync` | Generates TypeScript types for all Astro modules. [Learn more](https://docs.astro.build/en/reference/cli-reference/#astro-sync). | -| `pnpm run lint` | Lint with ESLint | -| `docker compose up -d` | Run AstroPaper on docker, You can access with the same hostname and port informed on `dev` command. | +| Command | Action | +| :------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------- | +| `pnpm install` | Installs dependencies | +| `pnpm run dev` | Starts local dev server at `localhost:4321` | +| `pnpm run build` | Build your production site to `./dist/` | +| `pnpm run preview` | Preview your build locally, before deploying | +| `pnpm run format:check` | Check code format with Prettier | +| `pnpm run format` | Format codes with Prettier | +| `pnpm run sync` | Generates TypeScript types for all Astro modules. [Learn more](https://docs.astro.build/en/reference/cli-reference/#astro-sync). | +| `pnpm run lint` | Lint with ESLint | +| `docker compose up -d` | Run AstroPaper on docker, You can access with the same hostname and port informed on `dev` command. | | `docker compose run app pnpm install` | You can run any command above into the docker container. | -| `docker build -t astropaper .` | Build Docker image for AstroPaper. | -| `docker run -p 4321:80 astropaper` | Run AstroPaper on Docker. The website will be accessible at `http://localhost:4321`. | +| `docker build -t astropaper .` | Build Docker image for AstroPaper. | +| `docker run -p 4321:80 astropaper` | Run AstroPaper on Docker. The website will be accessible at `http://localhost:4321`. | > **_Warning!_** Windows PowerShell users may need to install the [concurrently package](https://www.npmjs.com/package/concurrently) if they want to [run diagnostics](https://docs.astro.build/en/reference/cli-reference/#astro-check) during development (`astro check --watch & astro dev`). For more info, see [this issue](https://github.com/satnaing/astro-paper/issues/113). diff --git a/package.json b/package.json index 1954522..5c95368 100644 --- a/package.json +++ b/package.json @@ -44,4 +44,4 @@ "typescript": "^5.9.3", "typescript-eslint": "^8.51.0" } -} \ No newline at end of file +} diff --git a/src/components/Header.astro b/src/components/Header.astro index 5521784..a1a9e2d 100644 --- a/src/components/Header.astro +++ b/src/components/Header.astro @@ -76,13 +76,18 @@ const isActive = (path: string) => { Posts - {/*
  • + { + /*
  • Tags -
    • */} + */ + }
  • - + Publications
    • diff --git a/src/data/blog/publications/aic-ctu-at-averimatec.md b/src/data/blog/publications/aic-ctu-at-averimatec.md index 8cd0acd..aecbdb8 100644 --- a/src/data/blog/publications/aic-ctu-at-averimatec.md +++ b/src/data/blog/publications/aic-ctu-at-averimatec.md @@ -1,5 +1,5 @@ --- -title: "AIC CTU@AVerImaTeC: dual-retriever RAG for image-text fact checking" +title: "🥉 AIC CTU@AVerImaTeC: dual-retriever RAG for image-text fact checking" pubDatetime: 2026-02-15T00:00:00Z description: "arXiv preprint arXiv:2602.15190" tags: ["publications", "fact-checking", "rag"] @@ -20,11 +20,10 @@ citations: "N/A" ## Links - arXiv: [2602.15190](https://arxiv.org/abs/2602.15190) -- Google Scholar: [View profile](https://scholar.google.com/citations?user=1AZsqXEAAAAJ) ## Abstract -_TODO: Add abstract or summary._ +This paper introduces a dual-retriever RAG system for multimodal fact-checking, combining textual and image-aware evidence retrieval before verdict generation. The architecture is built to reduce hallucinations by forcing stronger evidence alignment across modalities. ## Resources @@ -35,4 +34,4 @@ _TODO: Add abstract or summary._ ## Notes -_TODO: Add notes, experiments, or follow-up material._ +A highlight of this project was a bronze-medal finish in AVeriTeC 2. Beyond leaderboard performance, we are proud that the system remained interpretable: retrieval traces made it easier to analyze failures and iterate quickly. diff --git a/src/data/blog/publications/aic-ctu-fever-8-long-context-rag.md b/src/data/blog/publications/aic-ctu-fever-8-long-context-rag.md index a114ccd..9aca71c 100644 --- a/src/data/blog/publications/aic-ctu-fever-8-long-context-rag.md +++ b/src/data/blog/publications/aic-ctu-fever-8-long-context-rag.md @@ -1,5 +1,5 @@ --- -title: "AIC CTU@FEVER 8: On-premise fact checking through long context RAG" +title: "🥇 AIC CTU@FEVER 8: On-premise fact checking through long context RAG" pubDatetime: 2025-09-01T00:00:00Z description: "Proceedings of the Eighth Fact Extraction and VERification Workshop (FEVER)" tags: ["publications", "fact-checking", "rag"] @@ -19,19 +19,17 @@ citations: 2 ## Links -- Google Scholar: [View profile](https://scholar.google.com/citations?user=1AZsqXEAAAAJ) - ## Abstract -_TODO: Add abstract or summary._ +Our FEVER 8 system explores on-premise fact-checking with long-context retrieval-augmented generation. We focus on practical deployment constraints, retrieval quality over long documents, and evidence-aware generation that keeps outputs grounded in retrieved passages. ## Resources -- Video: _TODO_ -- Slides: _TODO_ +- Video: [Underline lecture recording](https://underline.io/lecture/124235-aic-ctuatfever-8-on-premise-fact-checking-through-long-context-rag) +- Slides: [Underline presentation slides](https://underline.io/lecture/124235-aic-ctuatfever-8-on-premise-fact-checking-through-long-context-rag) - Code: _TODO_ - Dataset: _TODO_ ## Notes -_TODO: Add notes, experiments, or follow-up material._ +This submission reflects our preference for reproducible, controllable pipelines: instead of relying on closed hosted systems, we showed that competitive fact-checking can be done in an on-prem setup with careful long-context retrieval design. diff --git a/src/data/blog/publications/aic-ctu-system-at-averitec.md b/src/data/blog/publications/aic-ctu-system-at-averitec.md index f6ee880..fe10bab 100644 --- a/src/data/blog/publications/aic-ctu-system-at-averitec.md +++ b/src/data/blog/publications/aic-ctu-system-at-averitec.md @@ -1,5 +1,5 @@ --- -title: "AIC CTU system at AVeriTeC: Re-framing automated fact-checking as a simple RAG task" +title: "🥉 AIC CTU system at AVeriTeC: Re-framing automated fact-checking as a simple RAG task" pubDatetime: 2024-06-15T00:00:00Z description: "Proceedings of the Seventh Fact Extraction and VERification Workshop (FEVER)" tags: ["publications", "fact-checking", "rag"] @@ -20,19 +20,17 @@ citations: 10 ## Links -- Google Scholar: [View profile](https://scholar.google.com/citations?user=1AZsqXEAAAAJ) - ## Abstract -_TODO: Add abstract or summary._ +We recast automated fact-checking as a retrieval-augmented generation task: retrieve relevant evidence, then generate a verdict and justification directly from that evidence. The paper details a lightweight but effective pipeline and discusses where simplification helps versus where specialized modules are still needed. ## Resources -- Video: _TODO_ -- Slides: _TODO_ +- Video: [Underline lecture recording](https://underline.io/lecture/107018-aic-ctu-system-at-averitec-re-framing-automated-fact-checking-as-a-simple-rag-task) +- Slides: [Underline presentation slides](https://underline.io/lecture/107018-aic-ctu-system-at-averitec-re-framing-automated-fact-checking-as-a-simple-rag-task) - Code: _TODO_ - Dataset: _TODO_ ## Notes -_TODO: Add notes, experiments, or follow-up material._ +This was an important baseline paper for our team. It proved that a strong, well-tuned RAG approach can be surprisingly competitive, and it directly informed the system ideas we later pushed further in subsequent shared tasks. diff --git a/src/data/blog/publications/assessing-quality-of-information-extraction.md b/src/data/blog/publications/assessing-quality-of-information-extraction.md index 5b5a33e..f7c116e 100644 --- a/src/data/blog/publications/assessing-quality-of-information-extraction.md +++ b/src/data/blog/publications/assessing-quality-of-information-extraction.md @@ -25,11 +25,10 @@ citations: 11 ## Links - arXiv: [2404.04068](https://arxiv.org/abs/2404.04068) -- Google Scholar: [View profile](https://scholar.google.com/citations?user=1AZsqXEAAAAJ) ## Abstract -_TODO: Add abstract or summary._ +This work studies how to evaluate information extraction outputs beyond simple exact matching. We discuss practical quality dimensions (correctness, completeness, consistency, and usefulness), compare metric choices, and show where automatic scores diverge from human judgment for real extraction tasks. ## Resources @@ -40,4 +39,4 @@ _TODO: Add abstract or summary._ ## Notes -_TODO: Add notes, experiments, or follow-up material._ +I like this paper as a "methodology anchor" for later projects: before optimizing extraction models, we first make evaluation explicit and reliable. That framing helped us design cleaner experiments in downstream fact-checking and claim verification pipelines. diff --git a/src/data/blog/publications/claim-extraction-for-fact-checking.md b/src/data/blog/publications/claim-extraction-for-fact-checking.md index ccc6ceb..96aa976 100644 --- a/src/data/blog/publications/claim-extraction-for-fact-checking.md +++ b/src/data/blog/publications/claim-extraction-for-fact-checking.md @@ -21,11 +21,10 @@ citations: 2 ## Links - arXiv: [2502.04955](https://arxiv.org/abs/2502.04955) -- Google Scholar: [View profile](https://scholar.google.com/citations?user=1AZsqXEAAAAJ) ## Abstract -_TODO: Add abstract or summary._ +The work examines claim extraction as a dedicated subtask for fact-checking, introducing data, modeling strategies, and automatic metrics tailored to claim quality. It analyzes the trade-off between extracting many candidate claims and extracting claims that are specific, verifiable, and useful downstream. ## Resources @@ -36,4 +35,4 @@ _TODO: Add abstract or summary._ ## Notes -_TODO: Add notes, experiments, or follow-up material._ +In practice, this paper helped us treat claim extraction as a first-class modeling problem rather than a preprocessing detail. Better claim quality noticeably improved retrieval focus and final verification reliability in later pipelines. diff --git a/src/data/blog/publications/csfever-and-ctkfacts.md b/src/data/blog/publications/csfever-and-ctkfacts.md index 5f5e154..e802be6 100644 --- a/src/data/blog/publications/csfever-and-ctkfacts.md +++ b/src/data/blog/publications/csfever-and-ctkfacts.md @@ -22,11 +22,9 @@ citations: 19 ## Links -- Google Scholar: [View profile](https://scholar.google.com/citations?user=1AZsqXEAAAAJ) - ## Abstract -_TODO: Add abstract or summary._ +CsFEVER and CTKFacts introduce Czech-language resources for automated fact verification. The paper describes how claims and evidence were collected, annotated, and validated, and it highlights the challenges of balancing label quality, evidence grounding, and linguistic diversity in a lower-resource setting. ## Resources @@ -37,4 +35,4 @@ _TODO: Add abstract or summary._ ## Notes -_TODO: Add notes, experiments, or follow-up material._ +This dataset work was foundational for our later shared-task systems: it gave us Czech-centric data practices, annotation lessons, and realistic expectations about retrieval and evidence quality when moving from English benchmarks to multilingual fact-checking. diff --git a/src/data/blog/publications/pipeline-and-dataset-generation.md b/src/data/blog/publications/pipeline-and-dataset-generation.md index f225fc6..2ebf32c 100644 --- a/src/data/blog/publications/pipeline-and-dataset-generation.md +++ b/src/data/blog/publications/pipeline-and-dataset-generation.md @@ -21,11 +21,9 @@ citations: 9 ## Links -- Google Scholar: [View profile](https://scholar.google.com/citations?user=1AZsqXEAAAAJ) - ## Abstract -_TODO: Add abstract or summary._ +The paper presents an end-to-end pipeline for building automated fact-checking datasets in almost any language, covering claim harvesting, normalization, evidence linking, and verification labeling. It emphasizes scalable data creation while preserving enough quality control to support robust model training and evaluation. ## Resources @@ -36,4 +34,4 @@ _TODO: Add abstract or summary._ ## Notes -_TODO: Add notes, experiments, or follow-up material._ +For us, this was a key "from prototype to production" step: we moved from one-off dataset creation to a repeatable multilingual workflow that can be adapted to new domains and languages with manageable effort. diff --git a/src/pages/index.astro b/src/pages/index.astro index c99db41..28c5a65 100644 --- a/src/pages/index.astro +++ b/src/pages/index.astro @@ -53,7 +53,7 @@ const recentPosts = sortedPosts.filter(({ data }) => !data.featured);

    - PhD candidate at + PhD candidate at

    Publications are included here as a category: - + publications .

    diff --git a/src/pages/publications/index.astro b/src/pages/publications/index.astro index bb0041a..84d5cc0 100644 --- a/src/pages/publications/index.astro +++ b/src/pages/publications/index.astro @@ -23,10 +23,15 @@ const publications = getSortedPosts(posts).filter(
    -
    +

    Publications

    - Full list also on Google Scholar and ORCID. + Full list also on Google Scholar and ORCID.

    @@ -34,20 +39,21 @@ const publications = getSortedPosts(posts).filter( publications.map(publication => (

    - + {publication.data.title}

    - { - publication.data.authors && ( -

    {publication.data.authors.join(", ")}

    - ) - } - { - publication.data.venue && ( -

    {publication.data.venue}

    - ) - } + {publication.data.authors && ( +

    + {publication.data.authors.join(", ")} +

    + )} + {publication.data.venue && ( +

    {publication.data.venue}

    + )}

    {publication.data.pubDatetime.getUTCFullYear()} | Citations:{" "} {publication.data.citations ?? "N/A"}