Triple

T18625042
Position Surface form Disambiguated ID Type / Status
Subject Diocesan Synod of Blackburn E455257 entity
Predicate meetsAt P373 FINISHED
Object Blackburn NE NERFINISHED

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: Blackburn | Statement: [Diocesan Synod of Blackburn, meetsAt, Blackburn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Blackburn
Context triple: [Diocesan Synod of Blackburn, meetsAt, Blackburn]
  • A. Blackburn chosen
    Blackburn is a large industrial town in Lancashire, England, historically known for its textile manufacturing and located north of Manchester.
  • B. Blackburn
    Blackburn is a small town in West Lothian, Scotland, known primarily as a residential community within the Central Belt.
  • C. Blackburn Perth
    The Blackburn Perth was a British biplane flying boat of the interwar period, used primarily for long-range maritime patrol and reconnaissance by the Royal Air Force.
  • D. Bolton
    Bolton is a small town located in Hartford County in the U.S. state of Connecticut.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d38cc7948190a55ea64e5638994e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e54f039b408190b51fe770a4c530ec completed April 19, 2026, 9:54 p.m.
Created at: April 10, 2026, 11:46 a.m.