Triple

T22736495
Position Surface form Disambiguated ID Type / Status
Subject Havant Borough Council E562284 entity
Predicate hasJurisdictionOver P808 FINISHED
Object Bedhampton 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: Bedhampton | Statement: [Havant Borough Council, hasJurisdictionOver, Bedhampton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bedhampton
Context triple: [Havant Borough Council, hasJurisdictionOver, Bedhampton]
  • A. Bedhampton chosen
    Bedhampton is a suburban area and former village in Hampshire, England, situated near Havant on the south coast.
  • B. Paglesham
    Paglesham is a small rural village in Essex, England, known historically for its fishing, boatbuilding, and smuggling heritage along the River Roach.
  • C. Henham
    Henham is a small rural village located in the English county of Suffolk.
  • D. Kempshott
    Kempshott is a residential suburb of Basingstoke in Hampshire, England, known for its family housing and local amenities.
  • 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 (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_69e24550859c81908727d91efc3a81b4 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1796fc2a88190a4d86b421345b088 completed April 29, 2026, 3:22 a.m.
Created at: April 17, 2026, 3:22 p.m.