Triple

T33323365
Position Surface form Disambiguated ID Type / Status
Subject Llanberis station E853195 entity
Predicate isLowerTerminusOf P57205 FINISHED
Object Snowdon Mountain 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: Snowdon Mountain Railway | Statement: [Llanberis station, isLowerTerminusOf, Snowdon Mountain Railway]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isLowerTerminusOf
Context triple: [Llanberis station, isLowerTerminusOf, Snowdon Mountain Railway]
  • A. hasLowestTerminusAmong
    Indicates that one entity’s terminus (end point) is lower in position or elevation than the termini of all other compared entities.
  • B. hasTerminusIn
    Indicates that something (such as a route, line, or path) ends or has its final stopping point at a specified location.
  • C. hasTerminusRole
    Indicates that an entity participates in something specifically in the capacity of a terminus or endpoint role.
  • D. isMajorTerminalOf
    Indicates that one entity serves as a primary or main terminal (such as a key endpoint or hub) for another entity within a system or network.
  • E. lowerTerminus chosen
    Indicates that one entity serves as the lower endpoint or downstream terminus of another entity, such as a route, segment, or connection.
  • 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_69f349685f088190b8fda44083a018a9 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e3156ea48190b604e414665ef351 completed May 3, 2026, 5:54 a.m.
PD Predicate disambiguation batch_69f6de0b9ba48190887c9eb5d06a2e94 completed May 3, 2026, 5:32 a.m.
Created at: May 1, 2026, 1:33 a.m.