Triple

T8769414
Position Surface form Disambiguated ID Type / Status
Subject Bassingbourn E208418 entity
Predicate hasPostTown P2711 FINISHED
Object ROYSTON E742690 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: ROYSTON | Statement: [Bassingbourn, hasPostTown, ROYSTON]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ROYSTON
Context triple: [Bassingbourn, hasPostTown, ROYSTON]
  • A. ROYSTON chosen
    ROYSTON is a small market town in Hertfordshire, England, known for its historic crossroads location and the mysterious medieval Royston Cave.
  • B. Croston
    Croston is a historic village in Lancashire, England, known for its picturesque rural setting, traditional architecture, and riverside location.
  • C. Robertstown
    Robertstown is a small Irish village in County Kildare known for its historic canal-side setting and heritage as a former inland waterways hub.
  • D. Rishton
    Rishton is a village in the borough of Hyndburn in Lancashire, England, known historically for its role in the textile industry and as a former cotton mill town.
  • E. Weston
    Weston is a historic residential neighbourhood in the former city of York, now part of Toronto, Ontario, known for its village-like character and location along the Humber River.
  • 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_69ca835edb4481909b4aafb616dc5eb7 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5eedc7188190a67d959b9af53837 completed March 31, 2026, 11:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf51af01e48190af674a03d0768f3b completed April 3, 2026, 5:35 a.m.
Created at: March 30, 2026, 6:41 p.m.