Triple

T21412915
Position Surface form Disambiguated ID Type / Status
Subject Bedale E528219 entity
Predicate hasNearbyTown P3883 FINISHED
Object Leyburn 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: Leyburn | Statement: [Bedale, hasNearbyTown, Leyburn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leyburn
Context triple: [Bedale, hasNearbyTown, Leyburn]
  • A. Leyburn chosen
    Leyburn is a small market town in North Yorkshire, England, serving as a popular gateway and service hub for visitors to the Yorkshire Dales.
  • B. Slaidburn
    Slaidburn is a small, historic village in Lancashire, England, known for its traditional stone buildings and scenic setting within the Forest of Bowland Area of Outstanding Natural Beauty.
  • C. Cockburnspath
    Cockburnspath is a small coastal village in the Scottish Borders region of southeastern Scotland, near the North Sea and the border with England.
  • D. Ilkeston
    Ilkeston is a market town in the East Midlands of England, historically known for its coal mining and textile industries.
  • E. Fairton
    Fairton is a small rural settlement in New Zealand’s Canterbury region, situated within the Ashburton District and known for its agricultural surroundings.
  • 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_69e0c454c248819093425d1099101c09 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e8b20017d8819096b1a679edc8943a completed April 22, 2026, 11:33 a.m.
Created at: April 16, 2026, 5:44 p.m.