Triple

T8031389
Position Surface form Disambiguated ID Type / Status
Subject Manchester, Sheffield and Lincolnshire Railway interests (partial) E186986 entity
Predicate railwayCompanyInvolved P76977 FINISHED
Object Manchester, Sheffield and Lincolnshire Railway E223773 NE FINISHED

How this triple was built (3 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, Sheffield and Lincolnshire Railway | Statement: [Manchester, Sheffield and Lincolnshire Railway interests (partial), railwayCompanyInvolved, Manchester, Sheffield and Lincolnshire Railway]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Manchester, Sheffield and Lincolnshire Railway
Context triple: [Manchester, Sheffield and Lincolnshire Railway interests (partial), railwayCompanyInvolved, Manchester, Sheffield and Lincolnshire Railway]
  • A. Manchester, Sheffield and Lincolnshire Railway chosen
    The Manchester, Sheffield and Lincolnshire Railway was a 19th-century British railway company that operated lines across northern England and later evolved into the Great Central Railway.
  • B. York and North Midland Railway
    The York and North Midland Railway was an early 19th-century English railway company that played a key role in developing rail connections in Yorkshire and the surrounding regions.
  • C. Manchester and Leeds Railway
    The Manchester and Leeds Railway was a pioneering 19th-century British railway company that established one of the earliest major trans-Pennine rail routes between the industrial centers of Manchester and Leeds.
  • D. Hull and Barnsley Railway
    The Hull and Barnsley Railway was a late 19th-century British railway company serving the port city of Hull and surrounding areas, later absorbed into larger railway groupings.
  • E. Lancashire and Yorkshire Railway
    The Lancashire and Yorkshire Railway was a major pre-grouping British railway company that operated an extensive network of lines across industrial northern England during the 19th and early 20th centuries.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railwayCompanyInvolved
Context triple: [Manchester, Sheffield and Lincolnshire Railway interests (partial), railwayCompanyInvolved, Manchester, Sheffield and Lincolnshire Railway]
  • A. railwayCompany
    Indicates that one entity is a railway company that owns, operates, or manages railway services or infrastructure in relation to another entity.
  • B. railwayCompanyTestedOn
    Indicates that a railway company has been subjected to a test, evaluation, or assessment in relation to a specified entity or context.
  • C. railwayCompanyType
    Indicates the specific category or classification of a railway company in terms of its role, ownership, or operational type.
  • D. laterRailwayCompany
    Indicates that one railway company is the successor or later incarnation of another railway company.
  • E. relatedRailroad chosen
    Indicates that there is an association or connection between an entity and a specific railroad, such as ownership, operation, service, or historical linkage.
  • F. None of above.

Provenance (4 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_69ca82ae2d1081909dbfee42b41db419 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3eef921081908d0ea21f142c175a completed March 31, 2026, 3:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc63c911c081909751b614966d986c completed April 1, 2026, 12:16 a.m.
PD Predicate disambiguation batch_69cb049688208190b32088bd2c5930bc completed March 30, 2026, 11:17 p.m.
Created at: March 30, 2026, 5:22 p.m.