Triple

T33648200
Position Surface form Disambiguated ID Type / Status
Subject Pendre Works E862019 entity
Predicate heritageRailwaySite P59837 FINISHED
Object Talyllyn Railway 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: Talyllyn Railway | Statement: [Pendre Works, heritageRailwaySite, Talyllyn Railway]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heritageRailwaySite
Context triple: [Pendre Works, heritageRailwaySite, Talyllyn Railway]
  • A. railwayHeritageFeature chosen
    Indicates that something is a feature associated with railway heritage, such as historically significant railway structures, equipment, or related elements.
  • B. railwayHeritageFrom
    Indicates that something derives its historical or cultural significance from a particular railway or railway-related source.
  • C. heritageRailwayType
    Indicates the specific kind or classification of a heritage railway associated with an entity.
  • D. heritageRailwayUse
    Indicates that a railway line, infrastructure, or service is used for heritage or historical purposes rather than for regular commercial transport.
  • E. heritageRailwayAssociation
    Indicates a formal association or membership relationship between a railway entity and a heritage railway organization or governing body.
  • 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_69f349840ba881908e3bfce536aeb92b completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fccdd496048190bca801a8a9eecb62 completed May 7, 2026, 5:37 p.m.
PD Predicate disambiguation batch_69fcccee6240819084680887731ff64b completed May 7, 2026, 5:33 p.m.
Created at: May 1, 2026, 1:42 a.m.