Triple

T17378478
Position Surface form Disambiguated ID Type / Status
Subject Colne Valley Railway E422502 entity
Predicate near P350 FINISHED
Object Sible Hedingham 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: Sible Hedingham | Statement: [Colne Valley Railway, near, Sible Hedingham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sible Hedingham
Context triple: [Colne Valley Railway, near, Sible Hedingham]
  • A. Sible Hedingham chosen
    Sible Hedingham is a village and civil parish in Essex, England, known for its historic rural character and proximity to the medieval stronghold of Castle Hedingham.
  • B. Castle Hedingham
    Castle Hedingham is a historic village in Essex, England, best known for its well-preserved Norman castle, Hedingham Castle.
  • C. Stalham
    Stalham is a small market town in Norfolk, England, known as a gateway to the Norfolk Broads.
  • D. Cowlinge
    Cowlinge is a small rural village and civil parish located in the county of Suffolk in eastern England.
  • E. Hawkenbury
    Hawkenbury is a residential suburb and community area of Royal Tunbridge Wells in Kent, England.
  • 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_69d889d6535c81908be333c01deaec4e completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43a840cd08190af3385388afb8c8f completed April 19, 2026, 2:14 a.m.
Created at: April 10, 2026, 5:45 a.m.