Triple

T24880586
Position Surface form Disambiguated ID Type / Status
Subject South Tynedale Railway E622695 entity
Predicate builtOnFormerRouteOf P102403 FINISHED
Object Alston Line 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: Alston Line | Statement: [South Tynedale Railway, builtOnFormerRouteOf, Alston Line]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: builtOnFormerRouteOf
Context triple: [South Tynedale Railway, builtOnFormerRouteOf, Alston Line]
  • A. usesFormerRouteOf chosen
    Indicates that one route, service, or pathway currently follows all or part of the alignment or path that was previously used by another route.
  • B. formerRouteNumber
    Indicates that an entity previously had a specific route number before being renumbered, discontinued, or otherwise changed.
  • C. laterBuiltOverBy
    Indicates that a structure or feature was constructed at a later time on top of, or replacing, an earlier one.
  • D. locatedWithinFormer
    Indicates that one entity is or was geographically contained within the boundaries of another entity that no longer exists in its former administrative or territorial form.
  • E. formerlyLocatedOn
    Indicates that an entity was once located on or situated upon another entity, but is no longer in that position.
  • 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_69f43043512481909501a3979cac9947 completed May 1, 2026, 4:46 a.m.
PD Predicate disambiguation batch_69f420fd375c81908ea4a4e60b76ee8f completed May 1, 2026, 3:41 a.m.
Created at: April 18, 2026, 5:24 a.m.