Triple

T676250
Position Surface form Disambiguated ID Type / Status
Subject Kirkcaldy railway station E13082 entity
Predicate isKeyStopFor P3386 FINISHED
Object east coast of Scotland rail 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: east coast of Scotland rail services | Statement: [Kirkcaldy railway station, isKeyStopFor, east coast of Scotland rail services]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isKeyStopFor
Context triple: [Kirkcaldy railway station, isKeyStopFor, east coast of Scotland rail services]
  • A. isKeyStopOn chosen
    Indicates that a particular stop functions as a primary or significant stop along a specified route or service.
  • B. isKeyRegionFor
    Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
  • C. hasStopArea
    Indicates that an entity is associated with or contains a specific stop area, such as a designated location where vehicles stop.
  • D. keyState
    Indicates the current status or condition of a key (such as pressed, released, locked, or unlocked) in relation to an associated object or system.
  • E. hasKeyboard
    Indicates that one entity possesses or is equipped with a keyboard as a component or accessory.
  • 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_69a4933d3bf88190972041cd8cf143b9 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4a04b2ae881908a5c23453bef8572 completed March 1, 2026, 8:23 p.m.
PD Predicate disambiguation batch_69a49d1bbd0c81909cfbec30bd17bde7 completed March 1, 2026, 8:10 p.m.
Created at: March 1, 2026, 7:36 p.m.