Triple

T21540041
Position Surface form Disambiguated ID Type / Status
Subject Langwith Junction E531458 entity
Predicate locatedNear P294 FINISHED
Object Langwith 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: Langwith | Statement: [Langwith Junction, locatedNear, Langwith]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Langwith
Context triple: [Langwith Junction, locatedNear, Langwith]
  • A. Langwith chosen
    Langwith is a small village in Derbyshire, England, situated near the town of Shirebrook and known for its rural character and former mining community.
  • B. Lerryn
    Lerryn is a small riverside village in Cornwall, England, known for its picturesque setting on a tidal creek and historic stepping stones across the water.
  • C. Wyre
    Wyre is a district and local government area in Lancashire, England, named after the River Wyre and known for its mix of coastal towns and rural countryside.
  • D. Wyre
    Wyre is a small, sparsely populated island in the Orkney archipelago of Scotland, known for its tranquil landscape and archaeological sites.
  • E. Blagdon
    Blagdon is a rural village in North Somerset, England, known for its proximity to Blagdon Lake and the Mendip Hills.
  • 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_69e0c45f17148190949c330ab9c27706 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ee9d119e0c8190a207c0e8ae328a95 completed April 26, 2026, 11:17 p.m.
Created at: April 16, 2026, 6:28 p.m.