Triple

T20858804
Position Surface form Disambiguated ID Type / Status
Subject River Pang E513555 entity
Predicate hasNearbySettlement P4647 FINISHED
Object Bucklebury 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: Bucklebury | Statement: [River Pang, hasNearbySettlement, Bucklebury]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bucklebury
Context triple: [River Pang, hasNearbySettlement, Bucklebury]
  • A. Bucklebury chosen
    Bucklebury is a rural village and civil parish in West Berkshire, England, known for its historic character and association with the Middleton family, relatives of Catherine, Princess of Wales.
  • B. Horbury
    Horbury is a town in West Yorkshire, England, historically part of the Wakefield area and known for its industrial heritage and parish church.
  • C. Fockbury
    Fockbury is a small hamlet in Worcestershire, England, best known as the birthplace of the poet and classical scholar A. E. Housman.
  • D. Badbury
    Badbury is a small settlement in Wiltshire, England, situated near the village of Chiseldon and close to the prehistoric hillfort of Badbury Rings.
  • E. Buckland
    Buckland is a small historic community located within the Bull Run Mountains region of northern Virginia.
  • 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_69e0b4f5b01081909452f654d2fc3f50 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c3a9fd7881908ae4c5c63f64efc0 completed April 21, 2026, 12:24 a.m.
Created at: April 16, 2026, 12:44 p.m.