Triple

T22112341
Position Surface form Disambiguated ID Type / Status
Subject Lancaster district E546448 entity
Predicate contains P35 FINISHED
Object Carnforth 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: Carnforth | Statement: [Lancaster district, contains, Carnforth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Carnforth
Context triple: [Lancaster district, contains, Carnforth]
  • A. Clitheroe
    Clitheroe is a historic market town in northern England, known for its medieval castle and scenic location in the Ribble Valley.
  • 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. Millom
    Millom is a small coastal town in Cumbria, England, situated on the Duddon Estuary and historically known for its ironworks and mining industry.
  • D. Maghull
    Maghull is a suburban town in Merseyside, England, situated to the north of Liverpool and functioning largely as a residential commuter area.
  • E. CARNFORTH chosen
    Carnforth is a small market town in Lancashire, England, known historically as a railway junction and for its association with the film "Brief Encounter."
  • 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_69e11e38b3848190ac3a4fa97d56e65a completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1294ae7608190901745384a023bab completed April 28, 2026, 9:40 p.m.
Created at: April 16, 2026, 8:31 p.m.