Triple

T13879786
Position Surface form Disambiguated ID Type / Status
Subject Fylde district E333682 entity
Predicate contains P35 FINISHED
Object Kirkham E824463 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: Kirkham | Statement: [Fylde district, contains, Kirkham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kirkham
Context triple: [Fylde district, contains, Kirkham]
  • A. Kirkham chosen
    Kirkham is a small town in Lancashire, England, known historically for its textile industry and market-town character.
  • B. Laleham
    Laleham is a riverside village in Surrey, England, situated on the River Thames and known for its historic church, green spaces, and residential character.
  • C. Hackham
    Hackham is a southern suburb of Adelaide in South Australia, situated within the local government area of the City of Onkaparinga.
  • D. Oswaldkirk
    Oswaldkirk is a small rural village and civil parish in North Yorkshire, England, known for its historic church and scenic countryside setting.
  • E. Mirfield
    Mirfield is a small town in West Yorkshire, England, known for its position on major rail routes and its historic textile industry.
  • 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_69d81c5dd2d48190b7a5fc1e009de936 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de0be71d388190909290cad2c6daf5 completed April 14, 2026, 9:41 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c7100b308190bdd5feaa116ee5fe completed May 3, 2026, 10:07 p.m.
Created at: April 9, 2026, 10:15 p.m.