Triple

T17576993
Position Surface form Disambiguated ID Type / Status
Subject Barnetby E428094 entity
Predicate hasPostTown P2711 FINISHED
Object BARNETBY 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: BARNETBY | Statement: [Barnetby, hasPostTown, BARNETBY]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: BARNETBY
Context triple: [Barnetby, hasPostTown, BARNETBY]
  • A. Barnetby chosen
    Barnetby is a village and railway junction in North Lincolnshire, England, known for its busy rail connections on routes across northern and eastern England.
  • B. Barnby
    Barnby is a small rural village and civil parish located in the county of Suffolk in eastern England.
  • C. Barrowby
    Barrowby is a village in Lincolnshire, England, known for its rural character and proximity to the market town of Grantham.
  • D. Brocklesby
    Brocklesby is a small rural town in the Riverina region of New South Wales, Australia, known for its agricultural community and historic railway connections.
  • E. Barming
    Barming is a village and railway station in Kent, England, serving the western outskirts of Maidstone on the Medway Valley Line.
  • 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_69d889e0385081908a04b66f4dd4bd0d completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e463ca76848190a7beb6deb4b0f1a4 completed April 19, 2026, 5:10 a.m.
Created at: April 10, 2026, 5:50 a.m.