Triple

T12054302
Position Surface form Disambiguated ID Type / Status
Subject St James Church, Haslingden E287000 entity
Predicate locatedIn P40 FINISHED
Object Haslingden E53867 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: Haslingden | Statement: [St James Church, Haslingden, locatedIn, Haslingden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Haslingden
Context triple: [St James Church, Haslingden, locatedIn, Haslingden]
  • A. Haslingden chosen
    Haslingden is a small former mill town in Lancashire, England, known for its industrial heritage and location within the Rossendale Valley.
  • B. Mirfield
    Mirfield is a small town in West Yorkshire, England, known for its position on major rail routes and its historic textile industry.
  • C. Riddlesden
    Riddlesden is a residential suburb of Keighley in West Yorkshire, England, known for its mix of modern housing and historic sites such as the National Trust-owned East Riddlesden Hall.
  • D. Knottingley
    Knottingley is a small town in West Yorkshire, England, historically known for its glassmaking and situated on the banks of the River Aire.
  • E. Honley
    Honley is a large village in West Yorkshire, England, situated in the Holme Valley near Huddersfield.
  • 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_69d6ab4780948190bdb9f7620c2ac27e completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d90425258c8190ba7b3b837c439253 completed April 10, 2026, 2:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69f60a62f0fc8190a3d15ccfb23bb788 completed May 2, 2026, 2:29 p.m.
Created at: April 8, 2026, 9:47 p.m.