Triple

T1434140
Position Surface form Disambiguated ID Type / Status
Subject Cragside E30519 entity
Predicate locatedIn P40 FINISHED
Object Rothbury E33988 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: Rothbury | Statement: [Cragside, locatedIn, Rothbury]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rothbury
Context triple: [Cragside, locatedIn, Rothbury]
  • A. Rothbury chosen
    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.
  • B. Workington
    Workington is a coastal town and port on the west coast of England, historically known for its steel and coal industries and situated at the mouth of the River Derwent.
  • 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. Buckland
    Buckland is a small Inupiat community and city in northwestern Alaska situated along the Buckland River.
  • E. Buxton
    Buxton is a historic spa town in Derbyshire, England, renowned for its thermal mineral springs and Georgian architecture.
  • 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_69a498fc69ec8190b61722bd4b67c4d2 completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c500a9888190a16fbb1ec97a79c9 completed March 1, 2026, 11 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad0e6c095c8190ad881f8d5b22ce93 completed March 8, 2026, 5:51 a.m.
Created at: March 1, 2026, 8 p.m.