Triple

T15077405
Position Surface form Disambiguated ID Type / Status
Subject Bückeburg E380040 entity
Predicate hasTwinTown P919 FINISHED
Object Cramlington E259585 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: Cramlington | Statement: [Bückeburg, hasTwinTown, Cramlington]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cramlington
Context triple: [Bückeburg, hasTwinTown, Cramlington]
  • A. Cramlington chosen
    Cramlington is a modern, largely residential town in North East England known for its post-war development and proximity to Newcastle upon Tyne.
  • B. Didlington
    Didlington is a small village in Norfolk, England, known for its rural landscape, historic estate, and proximity to the River Wissey.
  • C. Morpeth
    Morpeth is a historic market town in Northumberland, England, known for its traditional architecture and role as a local commercial and administrative centre.
  • D. Hexham
    Hexham is a historic market town in Northumberland, England, known for its medieval abbey and proximity to Hadrian’s Wall.
  • E. 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.
  • 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_69d85cd7683881908d405c1b5d7b4f7f completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69dff7fe5a208190823900b25e298dab completed April 15, 2026, 8:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69fea5d2765481908f101bef483ed02f completed May 9, 2026, 3:11 a.m.
Created at: April 10, 2026, 3:03 a.m.