Triple

T4350668
Position Surface form Disambiguated ID Type / Status
Subject Sowerby Bridge railway station E98016 entity
Predicate hasFormerGoodsFacilities P29363 FINISHED
Object goods yard LITERAL 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: goods yard | Statement: [Sowerby Bridge railway station, hasFormerGoodsFacilities, goods yard]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFormerGoodsFacilities
Context triple: [Sowerby Bridge railway station, hasFormerGoodsFacilities, goods yard]
  • A. hasFacilities
    Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
  • B. hasFormerUse chosen
    Indicates that something previously served a particular function or role that it no longer has.
  • C. hasFormerService
    Indicates that an entity previously provided a service to another entity but no longer does so.
  • D. hasFormerSettlement
    Indicates that a location previously contained a settlement that no longer exists or is no longer inhabited.
  • E. hasFormerUseNearby
    Indicates that something in the vicinity previously had a particular use or function that is no longer current.
  • 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_69b3454965f881908c41190bb22f0e4b completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b351a99788819080b13a20124e49a0 completed March 12, 2026, 11:52 p.m.
PD Predicate disambiguation batch_69b34f51ed7c8190b7bf5f44b56b730d completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:15 p.m.