Triple

T5068037
Position Surface form Disambiguated ID Type / Status
Subject Liverpool South Parkway railway station E114190 entity
Predicate hasBusLink P39381 FINISHED
Object dedicated airport bus services 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: dedicated airport bus services | Statement: [Liverpool South Parkway railway station, hasBusLink, dedicated airport bus services]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBusLink
Context triple: [Liverpool South Parkway railway station, hasBusLink, dedicated airport bus services]
  • A. hasBusServices chosen
    Indicates that one location or entity is served by bus routes or bus transportation provided by another.
  • B. hasBusLoop
    Indicates that a location or facility includes a designated looped roadway or area specifically for bus circulation, stopping, or turning.
  • C. hasBusOperator
    Indicates that a bus service, route, or vehicle is operated or managed by a specific operator or company.
  • D. hasBusInterchange
    Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
  • E. hasBusPlatforms
    Indicates that a location or facility is equipped with one or more designated platforms for boarding or alighting from buses.
  • 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_69bd443cf28c8190ad371d603563dbdd completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd749dd1a08190858fa739df024eb4 completed March 20, 2026, 4:23 p.m.
PD Predicate disambiguation batch_69bd715622b48190a3e8e49a5ef62b4a completed March 20, 2026, 4:09 p.m.
Created at: March 20, 2026, 1:38 p.m.