Triple

T27243749
Position Surface form Disambiguated ID Type / Status
Subject ZKF E687281 entity
Predicate associatedMainlineStation P65507 FINISHED
Object London King’s Cross railway station 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: London King’s Cross railway station | Statement: [ZKF, associatedMainlineStation, London King’s Cross railway station]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedMainlineStation
Context triple: [ZKF, associatedMainlineStation, London King’s Cross railway station]
  • A. associatedStation chosen
    Indicates a relationship where one entity is linked or connected to a particular station as its relevant or related station.
  • B. formerMainlineStation
    Indicates that a station previously served as a mainline station but no longer holds that status.
  • C. connectsToRailStation
    Indicates that one entity has a direct link, route, or access connection to a rail station.
  • D. associatedWithStationName
    Indicates a relationship where something is linked or connected to a particular station identified by its name.
  • E. servesAsThroughStationFor
    Indicates that a station functions as an intermediate (through) stop for a particular service, route, or journey rather than as its starting or ending point.
  • 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_69ef355547408190b5ca0d777c65040a completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69ffc7b4c7f88190b6357a44e7f0940f completed May 9, 2026, 11:48 p.m.
PD Predicate disambiguation batch_69ffc755f09c8190995ca00d97336988 completed May 9, 2026, 11:46 p.m.
Created at: April 27, 2026, 10:39 a.m.