Triple

T14621276
Position Surface form Disambiguated ID Type / Status
Subject High Furness E343226 entity
Predicate borders P224 FINISHED
Object Low Furness E343225 NE FINISHED

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: Low Furness | Statement: [High Furness, borders, Low Furness]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Low Furness
Context triple: [High Furness, borders, Low Furness]
  • A. Low Furness chosen
    Low Furness is the southern, low-lying part of the Furness Peninsula in Cumbria, England, known for its rural landscapes, coastal scenery, and historic villages.
  • B. Furness Vale
    Furness Vale is a small village in Derbyshire, England, situated in the High Peak area of the Peak District.
  • C. Farndale
    Farndale is a scenic valley in the North York Moors of England, renowned for its springtime displays of wild daffodils along the River Dove.
  • D. Chollerford
    Chollerford is a small village in Northumberland, England, known as a key stopping point near Hadrian’s Wall and the River North Tyne.
  • E. Tilberthwaite
    Tilberthwaite is a scenic valley area in England's Lake District, known for its rugged fells, former slate quarries, and popular walking routes.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d822dffc3c8190aa173b90761bffda completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb466a61c81908a110d40fb959b6f completed April 14, 2026, 9:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69fda92688a08190bb27434acc7c12e7 completed May 8, 2026, 9:13 a.m.
Created at: April 10, 2026, 1:25 a.m.