Triple

T30684046
Position Surface form Disambiguated ID Type / Status
Subject Northfleet railway station E781133 entity
Predicate typicalOffPeakServiceToLondon P80227 FINISHED
Object trains to London Charing Cross 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: trains to London Charing Cross | Statement: [Northfleet railway station, typicalOffPeakServiceToLondon, trains to London Charing Cross]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalOffPeakServiceToLondon
Context triple: [Northfleet railway station, typicalOffPeakServiceToLondon, trains to London Charing Cross]
  • A. typicalOffPeakServiceTo chosen
    Indicates the usual or standard off-peak (non-peak time) service pattern that operates to a given destination.
  • B. typicalOffPeakTrainsPerHourToLondonWaterloo
    Indicates the usual number of trains per hour running to London Waterloo during off-peak times.
  • C. typicalOffPeakFrequencyToHastings
    Indicates how often, during typical off-peak times, a service or connection operates to Hastings.
  • D. offPeakServiceFrequency_minutes
    Indicates the number of minutes between successive services during off-peak periods.
  • E. servesCentralLondon
    Indicates that something provides service or access specifically to the Central London area.
  • 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_69f224a92f54819095499b4d32bd5134 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_6a037c876524819098545e6037d3107d completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379e2fac0819089b522db3260028c completed May 12, 2026, 7:05 p.m.
Created at: April 29, 2026, 8:33 p.m.