Triple

T23117199
Position Surface form Disambiguated ID Type / Status
Subject Loscoe E576787 entity
Predicate hasNeighbouringSettlement P4647 FINISHED
Object Codnor 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: Codnor | Statement: [Loscoe, hasNeighbouringSettlement, Codnor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Codnor
Context triple: [Loscoe, hasNeighbouringSettlement, Codnor]
  • A. Codnor chosen
    Codnor is a village in the Amber Valley district of Derbyshire, England, known historically for coal mining and its nearby medieval castle remains.
  • B. Brycheiniog
    Brycheiniog was an early medieval Welsh kingdom located in what is now Brecknockshire in south-central Wales.
  • C. Glyndyfrdwy
    Glyndyfrdwy is a village in Denbighshire, Wales, historically notable as the birthplace and early stronghold of the Welsh leader Owain Glyndŵr.
  • D. Towyn
    Towyn is a coastal town in North Wales known for its holiday parks, caravan sites, and seaside tourism.
  • E. Towyn
    Towyn is a coastal town in Gwynedd, Wales, known historically as a seaside resort and for its proximity to the Dysynni Valley and the Cambrian Coast railway.
  • 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_69e245f6c2e881909a228fdcfeb7c7d3 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18e4d095081908bad99fab6eaadd0 completed April 29, 2026, 4:51 a.m.
Created at: April 17, 2026, 3:59 p.m.