Triple

T26431021
Position Surface form Disambiguated ID Type / Status
Subject Sandhurst railway station E664508 entity
Predicate typicalOffPeakServiceToGatwickAirport 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, typicalOffPeakServiceToGatwickAirport, 2 trains per hour]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalOffPeakServiceToGatwickAirport
Context triple: [Sandhurst railway station, typicalOffPeakServiceToGatwickAirport, 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. typicalOffPeakFrequencyToHastings
    Indicates how often, during typical off-peak times, a service or connection operates to Hastings.
  • C. distanceToGatwickAirport
    Indicates the measured distance between a given entity’s location and Gatwick Airport.
  • D. secondaryLondonTerminal
    Indicates that a location serves as a secondary terminal in London associated with a primary London terminal for a given service or route.
  • E. distanceFromHeathrow
    Indicates the measured spatial distance between a given entity and Heathrow.
  • 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_69feb342994081909481ec8ec5d44928 completed May 9, 2026, 4:08 a.m.
PD Predicate disambiguation batch_69feb046e4e48190b96649aa28529cc9 completed May 9, 2026, 3:55 a.m.
Created at: April 26, 2026, 11:49 p.m.