Triple

T18697037
Position Surface form Disambiguated ID Type / Status
Subject Bishop of Burnley E457146 entity
Predicate hasSee P19510 FINISHED
Object Burnley 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: Burnley | Statement: [Bishop of Burnley, hasSee, Burnley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burnley
Context triple: [Bishop of Burnley, hasSee, 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. Burnley
    Burnley is an inner-city suburb of Melbourne, Victoria, known for its residential streets, parklands, and proximity to the Yarra River and major transport links.
  • C. Burnley F.C.
    Burnley F.C. is a professional English football club based in Burnley, Lancashire, known for its historic league titles and passionate local support.
  • D. Accrington
    Accrington is a town in Lancashire, England, historically known for its textile industry and the production of Accrington brick.
  • E. Bolton
    Bolton is a small town located in Hartford County in the U.S. state of Connecticut.
  • 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_69d8d392aad081909fe31aa03e6e97d1 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e562e8bc408190ab41b3c21003c249 completed April 19, 2026, 11:19 p.m.
Created at: April 10, 2026, 11:49 a.m.