Triple

T20258947
Position Surface form Disambiguated ID Type / Status
Subject North West Leicestershire E498779 entity
Predicate containsSettlement P847 FINISHED
Object Thringstone 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: Thringstone | Statement: [North West Leicestershire, containsSettlement, Thringstone]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thringstone
Context triple: [North West Leicestershire, containsSettlement, Thringstone]
  • A. Thringstone chosen
    Thringstone is a village in Leicestershire, England, known for its historic community, former mining connections, and proximity to the town of Coalville.
  • B. Windlestone
    Windlestone is a village in County Durham, England, known for its historic country house, Windlestone Hall, and its rural surroundings.
  • C. Stonethwaite
    Stonethwaite is a small rural village in the Borrowdale valley of England’s Lake District, known for its scenic landscapes and traditional stone-built houses.
  • D. Ingatestone
    Ingatestone is a historic village and civil parish in southeast England known for its traditional architecture and commuter links to London.
  • E. Shenstone
    Shenstone is a village in Staffordshire, England, served by a railway station on the Cross-City Line between Birmingham and Lichfield.
  • 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_69da6275fa6c8190952924930adee150 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e674c84e848190a6e8956698b84026 completed April 20, 2026, 6:47 p.m.
Created at: April 11, 2026, 11:41 p.m.