Triple

T21102491
Position Surface form Disambiguated ID Type / Status
Subject John Lehmann E519941 entity
Predicate placeOfBirth P1 FINISHED
Object Bourne End 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: Bourne End | Statement: [John Lehmann, placeOfBirth, Bourne End]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bourne End
Context triple: [John Lehmann, placeOfBirth, Bourne End]
  • A. Bourne End chosen
    Bourne End is a village in Buckinghamshire, England, situated on the River Thames between Marlow and Cookham.
  • B. Bourne End
    Bourne End is a village in Hertfordshire, England, situated in the Bulbourne Valley between Hemel Hempstead and Berkhamsted.
  • C. Ranmore
    Ranmore is a rural area in Surrey, England, known for its woodland landscapes within the Surrey Hills and its historic parish church of St Barnabas.
  • D. Cliffs End
    Cliffs End is a coastal village in Kent, England, overlooking Pegwell Bay and the Stour Estuary.
  • E. Berkeley Vale
    Berkeley Vale is a suburban locality on the Central Coast of New South Wales, Australia, known for its residential areas and proximity to waterways and natural reserves.
  • 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_69e0b508d8dc81909be940dafe36c8f7 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e71b5ee8948190ac6e9e144d312c90 completed April 21, 2026, 6:38 a.m.
Created at: April 16, 2026, 2:53 p.m.