Triple

T11360701
Position Surface form Disambiguated ID Type / Status
Subject Bawtry E269076 entity
Predicate postTown P2711 FINISHED
Object DONCASTER E123073 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: DONCASTER | Statement: [Bawtry, postTown, DONCASTER]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: DONCASTER
Context triple: [Bawtry, postTown, DONCASTER]
  • A. Doncaster chosen
    Doncaster is a large town and metropolitan borough in South Yorkshire, England, known historically for its railway heritage, horse racing, and role as a regional commercial center.
  • B. Yorkton
    Yorkton is a small city in southeastern Saskatchewan, Canada, known as a regional hub for agriculture and services.
  • C. Ancaster
    Ancaster is a village and civil parish in the South Kesteven district of Lincolnshire, England, known for its Roman history and archaeological remains.
  • D. Ancaster
    Ancaster is a historic community and former town now incorporated into the city of Hamilton, Ontario, Canada.
  • E. Scunthorpe
    Scunthorpe is an industrial town in North Lincolnshire, England, historically known for its steel production.
  • 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_69d6aacbe18081909e5fadb50082dd96 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7ea442e5c8190babfde25540b27e9 completed April 9, 2026, 6:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69e58bb3bd648190affa7ee85027c958 completed April 20, 2026, 2:13 a.m.
Created at: April 8, 2026, 9:33 p.m.