Triple

T22497255
Position Surface form Disambiguated ID Type / Status
Subject Belton E556173 entity
Predicate hasLandmark P105 FINISHED
Object Belton House 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: Belton House | Statement: [Belton, hasLandmark, Belton House]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Belton House
Context triple: [Belton, hasLandmark, Belton House]
  • A. Belton chosen
    Belton is a village and civil parish in the South Kesteven district of Lincolnshire, England, known for the historic Belton House and its surrounding estate.
  • B. Belton
    Belton is a small city in Anderson County, South Carolina, known for its historic downtown and annual Standpipe Festival.
  • C. Belton
    Belton is a small village and civil parish in the North West Leicestershire district of Leicestershire, England.
  • D. Belton
    Belton is a village and civil parish on the Isle of Axholme in North Lincolnshire, England.
  • E. Houghton Hall
    Houghton Hall is a grand 18th-century Palladian country house in Norfolk, England, renowned for its architecture, art collections, and role in British political history.
  • 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_69e11e5445bc8190b6a9481926db3355 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15cb31b8081909553fa860a07e746 completed April 29, 2026, 1:19 a.m.
Created at: April 16, 2026, 8:50 p.m.