Triple

T3958551
Position Surface form Disambiguated ID Type / Status
Subject Warrington Bank Quay railway station E85840 entity
Predicate hasDirectionOfServices P48943 FINISHED
Object services 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: services to London | Statement: [Warrington Bank Quay railway station, hasDirectionOfServices, services to London]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDirectionOfServices
Context triple: [Warrington Bank Quay railway station, hasDirectionOfServices, services to London]
  • A. serviceDirection
    Indicates the direction or orientation in which a service is provided or operates relative to involved entities.
  • B. servedByDirection chosen
    Indicates that something (such as a route, service, or facility) is provided or accessed in a specific directional orientation (e.g., northbound, inbound).
  • C. servesDirection
    Indicates that one entity provides service or functionality oriented toward, or in the direction of, another entity.
  • D. hasDirectionType
    Indicates that something possesses or is associated with a specific type or category of direction.
  • E. containsDirectionOf
    Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
  • 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_69aed93a96908190bcbdbfa718f155bd completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefaa5afdc8190b709af2473d75d02 completed March 9, 2026, 4:51 p.m.
PD Predicate disambiguation batch_69aef8ed04e4819096bced8971cd888d completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:31 p.m.