Triple

T8479007
Position Surface form Disambiguated ID Type / Status
Subject Manchester–Bury line E200466 entity
Predicate terminus P388 FINISHED
Object Bury E38579 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: Bury | Statement: [Manchester–Bury line, terminus, Bury]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bury
Context triple: [Manchester–Bury line, terminus, Bury]
  • A. Bury chosen
    Bury is a town in North West England known for its traditional market, historic textile industry roots, and preserved East Lancashire Railway.
  • B. Bolton
    Bolton is a large town in North West England known for its industrial heritage, particularly in textile manufacturing, and its location northwest of Manchester.
  • C. Bolton
    Bolton is a small town located in Hartford County in the U.S. state of Connecticut.
  • D. Bradford
    Bradford is a masculine given name of Old English origin, traditionally meaning "broad ford" and used both as a first name and surname.
  • E. Bradford
    Bradford is a major city in West Yorkshire, Northern England, known for its industrial heritage, diverse population, and role in the wool and textile industries.
  • 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_69ca831b17988190a1f3f3413d57b820 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe5216d6481908e25a49bcc2e00cc completed March 31, 2026, 3:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69cef2fa85ac8190adb7ddeb672bc550 completed April 2, 2026, 10:51 p.m.
Created at: March 30, 2026, 6:12 p.m.