Triple

T7800544
Position Surface form Disambiguated ID Type / Status
Subject Brierfield E180418 entity
Predicate district P2709 FINISHED
Object Pendle E329801 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: Pendle | Statement: [Brierfield, district, Pendle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pendle
Context triple: [Brierfield, district, Pendle]
  • A. Pendle chosen
    Pendle is a borough and district in Lancashire, England, best known for its rural landscapes around Pendle Hill and its association with the 17th-century Pendle witch trials.
  • B. Wyre
    Wyre is a district and local government area in Lancashire, England, named after the River Wyre and known for its mix of coastal towns and rural countryside.
  • C. Southwold
    Southwold is a small seaside town and popular tourist resort on the North Sea coast of Suffolk, England, known for its pier, beach huts, and historic lighthouse.
  • D. Southwold
    Southwold is a residential neighbourhood within the town of Bicester in Oxfordshire, England.
  • E. Aywick
    Aywick is a small coastal settlement on the island of Yell in Shetland, Scotland.
  • 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_69ca827e50cc8190a92a733577184938 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cae98765c48190b325eee67bd663fc completed March 30, 2026, 9:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69cb142117b48190bdc17677592bfa8f completed March 31, 2026, 12:24 a.m.
Created at: March 30, 2026, 4:33 p.m.