Triple

T17630541
Position Surface form Disambiguated ID Type / Status
Subject Hitchin and Harpenden E429963 entity
Predicate containsVillage P4011 FINISHED
Object Redbourn 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: Redbourn | Statement: [Hitchin and Harpenden, containsVillage, Redbourn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Redbourn
Context triple: [Hitchin and Harpenden, containsVillage, Redbourn]
  • A. Redbourn chosen
    Redbourn is a historic village and civil parish in Hertfordshire, England, situated near St Albans and known for its traditional English countryside character.
  • B. Stoneyburn
    Stoneyburn is a small village in West Lothian, Scotland, known historically for its coal mining roots and close-knit community.
  • C. Ridgmont
    Ridgmont is a small village and civil parish in Bedfordshire, England, known for its rural character and proximity to the Woburn Estate.
  • D. Umberleigh
    Umberleigh is a small rural village in North Devon, England, situated on the River Taw and served by a local railway station.
  • E. Hammerwood
    Hammerwood is a small rural locality in East Sussex, England, known for its countryside setting and proximity to regional routes.
  • 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_69d889e37f308190a6aa0a69daff86c7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46dc01b1c819099e3329cfb8cb77f completed April 19, 2026, 5:53 a.m.
Created at: April 10, 2026, 5:52 a.m.