Triple

T24880620
Position Surface form Disambiguated ID Type / Status
Subject South Tynedale Railway E622695 entity
Predicate laterStandardGaugeOperator P158132 FINISHED
Object British Railways 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: British Railways | Statement: [South Tynedale Railway, laterStandardGaugeOperator, British Railways]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: laterStandardGaugeOperator
Context triple: [South Tynedale Railway, laterStandardGaugeOperator, British Railways]
  • A. laterStandardGaugeOperator chosen
    Indicates that an entity became the standard-gauge operator of something at a later time, succeeding an earlier operator.
  • B. originalStandardGaugeOperator
    Indicates that an entity served as the initial or primary operator of a railway system using the standard track gauge.
  • C. operatedOnGauge
    Indicates that an entity has performed an operation or action on a gauge, affecting its state or readings.
  • D. nonStandardGauge
    Indicates that the gauge used in a railway or track segment deviates from the standard track gauge dimension.
  • E. convertedToStandardGauge
    Indicates that something previously using a different gauge has been changed or adapted to conform to a standard gauge specification.
  • F. None of above.

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_69e2fac4aa848190b3446a3922cec150 completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f47b865df48190bf4b6d3e9f9305e6 completed May 1, 2026, 10:08 a.m.
PD Predicate disambiguation batch_69f4682c8a3c8190adbfaac99474eaaf completed May 1, 2026, 8:45 a.m.
Created at: April 18, 2026, 5:24 a.m.