Triple

T5384409
Position Surface form Disambiguated ID Type / Status
Subject Buxton Opera House E113167 entity
Predicate location P40 FINISHED
Object Buxton E31898 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: Buxton | Statement: [Buxton Opera House, location, Buxton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Buxton
Context triple: [Buxton Opera House, location, Buxton]
  • A. Buxton
    Buxton is a village in Norfolk, England, known for its rural setting and historic association with the River Bure.
  • B. Buxton chosen
    Buxton is a historic spa town in Derbyshire, England, renowned for its thermal mineral springs and Georgian architecture.
  • C. Biddulph
    Biddulph is a small town in Staffordshire, England, known historically for its coal mining and rural surroundings.
  • D. Rothbury
    Rothbury is a historic market town and civil parish in Northumberland, England, situated on the River Coquet and known as a gateway to the Northumberland National Park.
  • E. Burtonwood
    Burtonwood is a village in Cheshire, England, historically associated with coal mining and the former RAF Burtonwood airbase.
  • 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_69bd4436a1988190af18dcff7fd306b4 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd86f39edc81908e53973cef1bc0f3 completed March 20, 2026, 5:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf3a96fba481909659b13425951068 completed March 22, 2026, 12:40 a.m.
Created at: March 20, 2026, 2:03 p.m.