Triple

T9445351
Position Surface form Disambiguated ID Type / Status
Subject Harpenden E227748 entity
Predicate adjacentTo P224 FINISHED
Object Redbourn E211881 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: Redbourn | Statement: [Harpenden, adjacentTo, Redbourn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Redbourn
Context triple: [Harpenden, adjacentTo, 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. Umberleigh
    Umberleigh is a small rural village in North Devon, England, situated on the River Taw and served by a local railway station.
  • D. Fruithurst
    Fruithurst is a small town in eastern Alabama, known historically for its fruit-growing and wine-making community.
  • E. Burtonwood
    Burtonwood is a village in Cheshire, England, historically associated with coal mining and the former RAF Burtonwood airbase.
  • 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_69ca843884488190ad6cbe0153088234 completed March 30, 2026, 2:10 p.m.
NER Named-entity recognition batch_69cd7f33deb88190bc74968575963ac4 completed April 1, 2026, 8:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69d110669ca48190bbaf772e2e6aa457 completed April 4, 2026, 1:21 p.m.
Created at: March 30, 2026, 7:51 p.m.