Triple

T7765895
Position Surface form Disambiguated ID Type / Status
Subject LA postcode area E176143 entity
Predicate containsPostTown P2711 FINISHED
Object Askam-in-Furness E343224 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: Askam-in-Furness | Statement: [LA postcode area, containsPostTown, Askam-in-Furness]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Askam-in-Furness
Context triple: [LA postcode area, containsPostTown, Askam-in-Furness]
  • A. Askam-in-Furness chosen
    Askam-in-Furness is a coastal village in Cumbria, England, historically linked to iron ore mining and overlooking the Duddon Estuary.
  • B. Furness Vale
    Furness Vale is a small village in Derbyshire, England, situated in the High Peak area of the Peak District.
  • C. Sandymoor
    Sandymoor is a residential suburb and civil parish in the Borough of Halton, Cheshire, England, known for its modern housing developments and proximity to Runcorn.
  • D. High Furness
    High Furness is the upland, largely rural and scenic northern part of the Furness Peninsula in Cumbria, England, known for its fells, forests, and proximity to the Lake District.
  • E. Much Hoole
    Much Hoole is a small rural village and civil parish in Lancashire, England, situated in the borough of South Ribble.
  • 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_69c69962923c8190ac74d28b4f9fe0a0 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c7043279748190b30882e9cc6cca54 completed March 27, 2026, 10:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8c7e1a1408190a802d4f4afb8dd05 completed March 29, 2026, 6:34 a.m.
Created at: March 27, 2026, 4:09 p.m.