Triple

T29847156
Position Surface form Disambiguated ID Type / Status
Subject Woodmansterne railway station E757959 entity
Predicate toCentralLondonTerminus P146904 FINISHED
Object London Victoria 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: London Victoria | Statement: [Woodmansterne railway station, toCentralLondonTerminus, London Victoria]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: toCentralLondonTerminus
Context triple: [Woodmansterne railway station, toCentralLondonTerminus, London Victoria]
  • A. toCentralLondonVia
    Indicates that something (such as a route, service, or connection) leads or travels to Central London by way of a specified path, mode, or intermediary location.
  • B. hasTerminusInCentralLondon chosen
    Indicates that the route, service, or line ends at a terminal point located within Central London.
  • C. primaryLondonTerminal
    Indicates that a given station serves as the main London terminal for a particular rail service or route.
  • D. originalLondonTerminusLocation
    Indicates the location of an entity’s original terminus station in London.
  • E. secondaryLondonTerminal
    Indicates that a location serves as a secondary terminal in London associated with a primary London terminal for a given service or route.
  • 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_69f2245a82cc8190a387e7d0118d710b completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f6764489c881909618ff635fe6c410 completed May 2, 2026, 10:10 p.m.
PD Predicate disambiguation batch_69f66ec5bf508190ad088b89455252bd completed May 2, 2026, 9:38 p.m.
Created at: April 29, 2026, 5:42 p.m.