Triple

T11495757
Position Surface form Disambiguated ID Type / Status
Subject BD postcode area E272529 entity
Predicate coversTown P847 FINISHED
Object Addingham E929121 NE FINISHED

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: Addingham | Statement: [BD postcode area, coversTown, Addingham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Addingham
Context triple: [BD postcode area, coversTown, Addingham]
  • A. Addingham chosen
    Addingham is a picturesque village in West Yorkshire, England, situated between Ilkley and Skipton on the River Wharfe.
  • B. Croftamie
    Croftamie is a small rural village in central Scotland, situated within the Stirling council area and known for its scenic countryside setting.
  • C. Colliston
    Colliston is a small rural village located within the Angus council area in eastern Scotland.
  • D. Coningham
    Coningham is an English-language surname borne by several notable figures, including military officers and politicians.
  • E. Dalmellington
    Dalmellington is a small village in East Ayrshire, Scotland, known as a gateway to the nearby Galloway Hills and surrounding upland countryside.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d6aae1b09881909ce2ded3fa0c14fa completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d85de183f08190abfa36eaabc61dc6 completed April 10, 2026, 2:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69e624c3691081908f2e448aebab40aa completed April 20, 2026, 1:06 p.m.
Created at: April 8, 2026, 9:36 p.m.