Triple

T14621324
Position Surface form Disambiguated ID Type / Status
Subject Duddon Estuary E343227 entity
Predicate nearbySettlement P350 FINISHED
Object Broughton-in-Furness E688283 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: Broughton-in-Furness | Statement: [Duddon Estuary, nearbySettlement, Broughton-in-Furness]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Broughton-in-Furness
Context triple: [Duddon Estuary, nearbySettlement, Broughton-in-Furness]
  • A. Broughton-in-Furness chosen
    Broughton-in-Furness is a small historic market town in Cumbria, England, situated near the Lake District National Park.
  • B. Dalton-in-Furness
    Dalton-in-Furness is a small historic market town in Cumbria, England, known as the former capital of the Furness area.
  • C. Workington
    Workington is a coastal town and port on the west coast of England, historically known for its steel and coal industries and situated at the mouth of the River Derwent.
  • D. Barrow-in-Furness
    Barrow-in-Furness is a coastal industrial town in Cumbria, England, historically known for its shipbuilding and submarine construction.
  • E. Gisburn
    Gisburn is a small rural village and civil parish in Lancashire, England, situated within the Ribble Valley district.
  • 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.