Triple

T22984160
Position Surface form Disambiguated ID Type / Status
Subject Leighlinbridge E571556 entity
Predicate hasNearbySettlement P4647 FINISHED
Object Old Leighlin NE NERFINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Old Leighlin | Statement: [Leighlinbridge, hasNearbySettlement, Old Leighlin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Old Leighlin
Context triple: [Leighlinbridge, hasNearbySettlement, Old Leighlin]
  • A. Old Leighlin chosen
    Old Leighlin is a historic village in County Carlow, Ireland, known for its early Christian monastic site and medieval cathedral.
  • B. Leixlip
    Leixlip is a town in County Kildare, Ireland, known for its historic castle, proximity to Dublin, and location at the confluence of the River Liffey and the Rye Water.
  • C. Kinlochaline
    Kinlochaline is a small rural settlement in the remote Morvern area of the Scottish Highlands, known for its scenic coastal landscape and proximity to Kinlochaline Castle.
  • D. Clanchy
    Clanchy is a surname variant of Clancy, typically of Irish origin.
  • E. Leighlinbridge
    Leighlinbridge is a historic village on the River Barrow in County Carlow, Ireland, known for its ancient bridge and strategic medieval significance.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69e245b3c50481908bb3741ec9f40862 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18298637c819086fca34d55bad22d completed April 29, 2026, 4:01 a.m.
Created at: April 17, 2026, 3:49 p.m.