Triple

T20455318
Position Surface form Disambiguated ID Type / Status
Subject Hartington and Taddington ward E501761 entity
Predicate hasSettlement P1068 FINISHED
Object Hartington 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: Hartington | Statement: [Hartington and Taddington ward, hasSettlement, Hartington]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hartington
Context triple: [Hartington and Taddington ward, hasSettlement, Hartington]
  • A. Hartington chosen
    Hartington is a village and civil parish in Derbyshire, England, historically associated with the Cavendish family and the title Marquess of Hartington.
  • B. Highton
    Highton is a residential suburb of Geelong in Victoria, Australia, known for its hilly terrain, family-friendly amenities, and views over the Barwon River.
  • C. Harvington
    Harvington is a village and civil parish in Worcestershire, England, known for its historic character and rural setting within the Wychavon district.
  • D. Hempton
    Hempton is a small village in Norfolk, England, situated close to the market town of Fakenham.
  • E. Honington
    Honington is a small rural village and civil parish in Suffolk, England, known for its agricultural surroundings and proximity to RAF Honington.
  • 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_69e0b4ad4940819098cf2ff6413574e5 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e696a0dd188190ab6cbb387d9c0c1d completed April 20, 2026, 9:12 p.m.
Created at: April 16, 2026, 11:32 a.m.