Triple

T20643515
Position Surface form Disambiguated ID Type / Status
Subject Manchester–Bolton corridor E507290 entity
Predicate connects P390 FINISHED
Object Manchester 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: Manchester | Statement: [Manchester–Bolton corridor, connects, Manchester]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Manchester
Context triple: [Manchester–Bolton corridor, connects, Manchester]
  • A. Manchester
    Manchester is a historic neighborhood on Pittsburgh’s North Side known for its 19th-century architecture and designation as a historic district.
  • B. Manchester
    Manchester is a suburban town in central Connecticut known for its historic mills, shopping districts, and residential communities within the Greater Hartford area.
  • C. Manchester
    Manchester is a common English surname, notably borne by American singer and songwriter Melissa Manchester.
  • D. Manchester
    Manchester is a historic former settlement in what is now Cuyahoga Falls, Ohio, that served as an early name and precursor community to the modern city.
  • E. Manchester chosen
    Manchester is a major city in northwest England known for its industrial heritage, vibrant cultural scene, and influential contributions to music, sport, and science.
  • 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_69e0b4be702c8190a3d2410a881d310a completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6af1c51f48190abba54a5aace9fc8 completed April 20, 2026, 10:56 p.m.
Created at: April 16, 2026, 11:43 a.m.