Triple

T5830362
Position Surface form Disambiguated ID Type / Status
Subject Manchester–Preston railway corridor E129329 entity
Predicate connects P390 FINISHED
Object Preston E24766 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: Preston | Statement: [Manchester–Preston railway corridor, connects, Preston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Preston
Context triple: [Manchester–Preston railway corridor, connects, Preston]
  • A. Preston chosen
    Preston is a historic industrial city in Lancashire, England, known for its role in the Industrial Revolution and its status as a major urban center in the North West.
  • B. Preston
    Preston is a locality within the Dover District of Kent, England, known as a small rural village community.
  • C. Preston
    Preston is a masculine given name of English origin that has been used both as a first name and a surname.
  • D. Prenton
    Prenton is a suburban residential area on the Wirral Peninsula in Merseyside, England, known for its parks, schools, and proximity to Birkenhead.
  • E. East Preston
    East Preston is a coastal village in West Sussex, England, situated within the Arun District and known for its residential character and seaside location.
  • 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_69c00849d55481908b4f9f5543e0bf6d completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0346905848190a8f541401da05604 completed March 22, 2026, 6:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0b0d1ddb48190a697f202b43cc633 completed March 23, 2026, 3:17 a.m.
Created at: March 22, 2026, 3:54 p.m.