Triple

T25566043
Position Surface form Disambiguated ID Type / Status
Subject Highams Park railway station E640838 entity
Predicate typicalOffPeakServiceToChingford P80227 FINISHED
Object 4 trains per hour 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: 4 trains per hour | Statement: [Highams Park railway station, typicalOffPeakServiceToChingford, 4 trains per hour]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalOffPeakServiceToChingford
Context triple: [Highams Park railway station, typicalOffPeakServiceToChingford, 4 trains per hour]
  • A. typicalOffPeakServiceTo chosen
    Indicates the usual or standard off-peak (non-peak time) service pattern that operates to a given destination.
  • B. typicalOffPeakFrequencyToHastings
    Indicates how often, during typical off-peak times, a service or connection operates to Hastings.
  • C. adjacentStationTowardsChingford
    Indicates that one station is directly next to another along the rail line in the direction heading toward Chingford.
  • D. offPeakServiceFrequency_minutes
    Indicates the number of minutes between successive services during off-peak periods.
  • E. offPeakServicePattern
    Indicates the service pattern or schedule that applies during off-peak (non-rush-hour) times.
  • 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_69e75dc1beb08190bac7d76b8d6e7bc4 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69fd553d7cb881908d243e7a9f30ac85 completed May 8, 2026, 3:15 a.m.
PD Predicate disambiguation batch_69fd514dcb1c81908333c70d7edd79c9 completed May 8, 2026, 2:58 a.m.
Created at: April 21, 2026, 3:49 p.m.