Triple

T3644959
Position Surface form Disambiguated ID Type / Status
Subject River Bure E77275 entity
Predicate flowsThrough P225 FINISHED
Object Hoveton E300340 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: Hoveton | Statement: [River Bure, flowsThrough, Hoveton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hoveton
Context triple: [River Bure, flowsThrough, Hoveton]
  • A. Kempshott
    Kempshott is a residential suburb of Basingstoke in Hampshire, England, known for its family housing and local amenities.
  • B. Rustington
    Rustington is a large coastal village and civil parish on the English Channel in the Arun District of West Sussex, England.
  • C. Wadhurst
    Wadhurst is a rural village in East Sussex, England, known for its historic High Street, surrounding Wealden countryside, and role as a commuter community for nearby towns and London.
  • D. Wroxham chosen
    Wroxham is a village in Norfolk, England, widely regarded as the main boating and tourist centre of the Norfolk Broads.
  • E. Dereham
    Dereham is a market town in the English county of Norfolk, known historically for its agriculture and rural character.
  • 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_69ad85de1b988190a45f8dbfebc806fc completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc35da84c81908950de92ba171fa3 completed March 8, 2026, 6:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69b44f35985081909a499f9c1668b589 completed March 13, 2026, 5:53 p.m.
Created at: March 8, 2026, 3:24 p.m.