Triple

T10178080
Position Surface form Disambiguated ID Type / Status
Subject Bookham E235905 entity
Predicate hasPart P35 FINISHED
Object Little Bookham E235905 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: Little Bookham | Statement: [Bookham, hasPart, Little Bookham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Little Bookham
Context triple: [Bookham, hasPart, Little Bookham]
  • A. Bookham chosen
    Bookham is a village in Surrey, England, known for its residential character and proximity to the North Downs countryside.
  • B. Little Hadham
    Little Hadham is a small rural village and civil parish in Hertfordshire, England, known for its historic church, countryside setting, and location near the A120 between Bishop’s Stortford and Ware.
  • C. Little Berkhamsted
    Little Berkhamsted is a small rural village and civil parish in the county of Hertfordshire, England.
  • D. Little Glemham
    Little Glemham is a small rural village in the English county of Suffolk, known for its historic church and proximity to the Suffolk Coast and Heaths Area of Outstanding Natural Beauty.
  • E. Haddenham
    Haddenham is a large village in Buckinghamshire, England, known for its historic architecture and rural setting near the town of Thame.
  • 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_69ca84d1d5f88190ab878a1021ecff68 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdecd620808190892c6e3074500280 completed April 2, 2026, 4:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69d3012d11488190a410d389034da887 completed April 6, 2026, 12:41 a.m.
Created at: March 30, 2026, 9:11 p.m.