Triple

T6764453
Position Surface form Disambiguated ID Type / Status
Subject Sedgefield E154680 entity
Predicate containsTown P847 FINISHED
Object Shildon E151214 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: Shildon | Statement: [Sedgefield, containsTown, Shildon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shildon
Context triple: [Sedgefield, containsTown, Shildon]
  • A. Shildon chosen
    Shildon is a town in County Durham, England, historically significant as a cradle of the railway industry and home to major railway heritage attractions.
  • B. Didlington
    Didlington is a small village in Norfolk, England, known for its rural landscape, historic estate, and proximity to the River Wissey.
  • C. South Shields
    South Shields is a coastal town in Tyne and Wear, England, known historically for its shipbuilding and as part of the Tyneside urban area.
  • D. Morpeth
    Morpeth is a historic market town in Northumberland, England, known for its traditional architecture and role as a local commercial and administrative centre.
  • E. Shenley
    Shenley is a village and civil parish in the county of Hertfordshire in southern England, known for its residential character and proximity to London.
  • 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_69c688109c1c8190added9a221292af0 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d217bbfc81908c9e55efaf7f8594 completed March 27, 2026, 6:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69c712b9e7f081909d9fcc219ac525b8 completed March 27, 2026, 11:28 p.m.
Created at: March 27, 2026, 2:12 p.m.