Triple

T7789539
Position Surface form Disambiguated ID Type / Status
Subject Wyre E187341 entity
Predicate hasAdministrativeHeadquarters P1474 FINISHED
Object Poulton-le-Fylde E201718 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: Poulton-le-Fylde | Statement: [Wyre, hasAdministrativeHeadquarters, Poulton-le-Fylde]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Poulton-le-Fylde
Context triple: [Wyre, hasAdministrativeHeadquarters, Poulton-le-Fylde]
  • A. Poulton-le-Fylde chosen
    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.
  • B. Clitheroe
    Clitheroe is a historic market town in northern England, known for its medieval castle and scenic location in the Ribble Valley.
  • C. Lytham St Annes
    Lytham St Annes is a seaside town in Lancashire, England, known for its sandy beaches, Victorian architecture, and traditional resort character.
  • 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. 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_69ca82af2d2c8190963861f5e0b8bf21 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cae7ea13f08190a60c5f1863bce816 completed March 30, 2026, 9:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69caf62c8568819090c058b0c55b7865 completed March 30, 2026, 10:16 p.m.
Created at: March 30, 2026, 4:25 p.m.