Triple

T34558304
Position Surface form Disambiguated ID Type / Status
Subject Dublin to Cork railway line E887267 entity
Predicate endingStationInCork P19517 FINISHED
Object Cork Kent railway station 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: Cork Kent railway station | Statement: [Dublin to Cork railway line, endingStationInCork, Cork Kent railway station]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: endingStationInCork
Context triple: [Dublin to Cork railway line, endingStationInCork, Cork Kent railway station]
  • A. distanceFromCorkCity
    Indicates the spatial distance between a given place and Cork City.
  • B. railwayUpperTerminus
    Indicates that a railway line or route reaches its upper (typically higher-altitude or upstream) terminal endpoint at the related location.
  • C. formerTerminalStation
    Indicates that a location once served as the end point (terminus) of a transportation line or route but no longer holds that status.
  • D. terminalStationSouth chosen
    Indicates that a given station serves as the southern terminal (end point) of a particular route or line.
  • E. futureTerminusStation
    Indicates that a station is designated to become a terminus (end point) of a transit line or route at a specified future time.
  • 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_69f349d0c4d881908dd0950f5eb9ec0a completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7206146a881909110085fb46c8251 completed May 3, 2026, 10:16 a.m.
PD Predicate disambiguation batch_69f71cc8074c81909ae09bea2acf1a09 completed May 3, 2026, 10 a.m.
Created at: May 1, 2026, 2:02 a.m.