Skip to content

Temporal reasoning fails on overlapping date ranges #3

Description

@harneet2512

Bug

When two claims have overlapping temporal validity windows, the retrieval pipeline returns the older claim instead of the most recent one.

Repro:

  1. Store: "Meeting with Priya moved to Thursday" (May 15)
  2. Store: "Meeting with Priya moved to Friday" (May 18)
  3. Query: "When is the meeting with Priya?"
  4. Expected: Friday | Actual: Thursday

Root Cause

supersession.py checks exact-match on subject+predicate but the temporal overlap isn't triggering supersession because the value differs.

Fix

Add temporal proximity check in supersession_semantic.py — if two claims share subject+predicate and their timestamps are within a configurable window, the newer one supersedes.

Priority: High | Category: temporal-reasoning

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions