Triple

T1589625
Position Surface form Disambiguated ID Type / Status
Subject Pendle Hill E34148 entity
Predicate near P350 FINISHED
Object Burnley E39907 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: Burnley | Statement: [Pendle Hill, near, Burnley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burnley
Context triple: [Pendle Hill, near, Burnley]
  • A. Burnley chosen
    Burnley is a large market town in Lancashire, England, known historically for its textile industry and more recently for its football club, Burnley F.C.
  • B. Bolton
    Bolton is a large town in North West England known for its industrial heritage, particularly in textile manufacturing, and its location northwest of Manchester.
  • C. Rochdale
    Rochdale is a large town in Greater Manchester, England, historically known as a mill town and cooperative movement birthplace, now serving as a residential and commercial hub connected by rail to Manchester.
  • D. Blackburn
    Blackburn is a large industrial town in Lancashire, England, historically known for its textile manufacturing and located north of Manchester.
  • E. Bury
    Bury is a town in North West England known for its traditional market, historic textile industry roots, and preserved East Lancashire Railway.
  • 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_69a885fceb2c8190b47e0f7c0aefbff0 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a9090e251c81909ebb21a6b6262303 completed March 5, 2026, 4:39 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad469eaf588190ac6db1c8fb7fa04e completed March 8, 2026, 9:51 a.m.
Created at: March 4, 2026, 7:27 p.m.