Triple

T23383045
Position Surface form Disambiguated ID Type / Status
Subject Uckfield railway station E593802 entity
Predicate serviceFrequencyWeekdayPeak P115690 FINISHED
Object approximately 2 trains per hour to London 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: approximately 2 trains per hour to London | Statement: [Uckfield railway station, serviceFrequencyWeekdayPeak, approximately 2 trains per hour to London]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: serviceFrequencyWeekdayPeak
Context triple: [Uckfield railway station, serviceFrequencyWeekdayPeak, approximately 2 trains per hour to London]
  • A. offPeakServiceFrequency_minutes
    Indicates the number of minutes between successive services during off-peak periods.
  • B. typicalFrequencyWeekdayDaytime
    Indicates the usual or most common frequency with which something occurs during daytime hours on weekdays.
  • C. hasPeakHourFrequency chosen
    Indicates how often a service or event occurs during designated peak hours.
  • D. peakHours
    Indicates that an action, event, or condition occurs during the busiest or most heavily trafficked time period.
  • E. populationPeakPeriod
    Indicates the time period during which a population reached its highest recorded level.
  • 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_69e25d268a50819095f2fd479da8ef3f completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a3b9287481908fd86c41f6d9fc53 completed April 29, 2026, 6:22 a.m.
PD Predicate disambiguation batch_69f061dde2e481908308952f9c0d3c2e completed April 28, 2026, 7:29 a.m.
Created at: April 17, 2026, 5:34 p.m.