Triple

T11795083
Position Surface form Disambiguated ID Type / Status
Subject Ribble catchment E280484 entity
Predicate containsTown P847 FINISHED
Object Lytham St Annes E556792 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: Lytham St Annes | Statement: [Ribble catchment, containsTown, Lytham St Annes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lytham St Annes
Context triple: [Ribble catchment, containsTown, Lytham St Annes]
  • A. Lytham St Annes chosen
    Lytham St Annes is a seaside town in Lancashire, England, known for its sandy beaches, Victorian architecture, and traditional resort character.
  • B. Poulton-le-Fylde
    Poulton-le-Fylde is a historic market town in Lancashire, England, known for its traditional town centre and proximity to the seaside resort of Blackpool.
  • C. Cleveleys
    Cleveleys is a seaside town on the Fylde Coast in Lancashire, England, known for its promenade, beaches, and role as a residential and holiday destination.
  • D. Millom
    Millom is a small coastal town in Cumbria, England, situated on the Duddon Estuary and historically known for its ironworks and mining industry.
  • E. Southport
    Southport is a small city located within Marion County in the U.S. state of Indiana.
  • 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_69d6ab258b808190b1735835c841e3a4 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a5a082d08190a42541396a06ed98 completed April 10, 2026, 7:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69f130fd7b9881909e79ecb49fe98d30 completed April 28, 2026, 10:13 p.m.
Created at: April 8, 2026, 9:42 p.m.