Triple

T22502453
Position Surface form Disambiguated ID Type / Status
Subject Bewdley Bridge E556308 entity
Predicate namedAfter P63 FINISHED
Object Bewdley 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: Bewdley | Statement: [Bewdley Bridge, namedAfter, Bewdley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bewdley
Context triple: [Bewdley Bridge, namedAfter, Bewdley]
  • A. Bewdley chosen
    Bewdley is a historic riverside town in Worcestershire, England, known for its Georgian architecture and picturesque setting on the River Severn.
  • B. Bewley
    Bewley is an English-language surname borne by various notable individuals across fields such as acting, sports, and public service.
  • C. Bardwell
    Bardwell is a small city in western Kentucky that serves as the administrative and governmental center of Carlisle County.
  • D. Bardwell
    Bardwell is a small rural village and civil parish in the county of Suffolk in eastern England.
  • E. Bywell
    Bywell is a small historic village in Northumberland, England, situated on the north bank of the River Tyne and known for its medieval churches and castle ruins.
  • 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_69e11e5445bc8190b6a9481926db3355 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15cb6b47481909855fe93e95da7e7 completed April 29, 2026, 1:19 a.m.
Created at: April 16, 2026, 8:50 p.m.