Triple

T1375441
Position Surface form Disambiguated ID Type / Status
Subject White Peak E29210 entity
Predicate hasSettlement P1068 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: [White Peak, hasSettlement, Buxton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Buxton
Context triple: [White Peak, hasSettlement, Buxton]
  • A. Buxton chosen
    Buxton is a historic spa town in Derbyshire, England, renowned for its thermal mineral springs and Georgian architecture.
  • B. 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.
  • C. Ashbourne
    Ashbourne is a historic market town in Derbyshire, England, known for its traditional architecture and annual Royal Shrovetide Football match.
  • D. Buckland
    Buckland is a small Inupiat community and city in northwestern Alaska situated along the Buckland River.
  • E. Branxton
    Branxton is a small rural town in New South Wales, Australia, situated in the Hunter Region and known as a gateway to the Hunter Valley wine country.
  • 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_69a498d883a48190bfdca525296ef7ee completed March 1, 2026, 7:51 p.m.
NER Named-entity recognition batch_69a4c2f7aeb08190b52ef1058c18327e completed March 1, 2026, 10:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69acd485e7e48190b4c2dcec53ebe195 completed March 8, 2026, 1:44 a.m.
Created at: March 1, 2026, 7:59 p.m.