Triple

T28292268
Position Surface form Disambiguated ID Type / Status
Subject Surbiton railway station E713459 entity
Predicate hasFastServicesTo P56946 FINISHED
Object central London NE NERFINISHED

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: central London | Statement: [Surbiton railway station, hasFastServicesTo, central London]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFastServicesTo
Context triple: [Surbiton railway station, hasFastServicesTo, central London]
  • A. hasServiceTo
    Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
  • B. hasServiceSpeed chosen
    Indicates that an entity provides a service operating at a specified speed or performance rate.
  • C. hasFrequentServices
    Indicates that one entity regularly provides or receives services from another entity at short or recurring intervals.
  • D. hasDirectServices
    Indicates that one entity provides services directly to another entity without intermediaries.
  • E. hasCommercialServices
    Indicates that one entity provides or offers commercial services to another entity or within a specified context.
  • 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_69efb52371d88190a1381c4e58a3b731 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69f707f7959881908f037f0d6b1d0c36 completed May 3, 2026, 8:31 a.m.
PD Predicate disambiguation batch_69f700fc274c8190a128593dc7c7abd0 completed May 3, 2026, 8:02 a.m.
Created at: April 27, 2026, 11:30 p.m.