Triple

T26431020
Position Surface form Disambiguated ID Type / Status
Subject Sandhurst railway station E664508 entity
Predicate typicalOffPeakServiceToReading P80227 FINISHED
Object 2 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: 2 trains per hour | Statement: [Sandhurst railway station, typicalOffPeakServiceToReading, 2 trains per hour]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalOffPeakServiceToReading
Context triple: [Sandhurst railway station, typicalOffPeakServiceToReading, 2 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. hasOffPeakUsage
    Indicates that an entity exhibits or is associated with usage occurring during designated off-peak times rather than standard peak periods.
  • C. typicalOffPeakFrequencyToHastings
    Indicates how often, during typical off-peak times, a service or connection operates to Hastings.
  • D. hasPeakOffPeakDifferentiation
    Indicates that there is a distinction between peak and off-peak periods in how something is applied, priced, or operated.
  • E. offPeakServiceFrequency_minutes
    Indicates the number of minutes between successive services during off-peak periods.
  • 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_69ee883ad6a4819088f918e76122d690 completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69feafa1ba0081909013800b85a9f613 completed May 9, 2026, 3:53 a.m.
PD Predicate disambiguation batch_69feae58d62c81909d031f3df8992883 completed May 9, 2026, 3:47 a.m.
Created at: April 26, 2026, 11:49 p.m.