Triple

T17635479
Position Surface form Disambiguated ID Type / Status
Subject Ropley railway station E430081 entity
Predicate hasFootbridgeOrigin P128354 FINISHED
Object brought from a former Network Rail location 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: brought from a former Network Rail location | Statement: [Ropley railway station, hasFootbridgeOrigin, brought from a former Network Rail location]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFootbridgeOrigin
Context triple: [Ropley railway station, hasFootbridgeOrigin, brought from a former Network Rail location]
  • A. hasFootbridge
    Indicates that there exists a footbridge providing a pedestrian connection between the related entities.
  • B. hasTrailDistanceToFootbridge
    Indicates the length of the trail segment separating a given location or feature from a specified footbridge.
  • C. hasBridgeTo
    Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
  • D. hasBridgeTypeCrossing
    Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
  • E. hasSkyBridgeLocation
    Indicates that one entity is the location where a sky bridge is situated or connected.
  • F. None of above. chosen

Provenance (4 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_69d889e37f308190a6aa0a69daff86c7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46de0ad988190b1a2c0bff69eb9f1 completed April 19, 2026, 5:53 a.m.
PD Predicate disambiguation batch_69e3cddc87188190ac2f049b86038676 completed April 18, 2026, 6:30 p.m.
PDg Predicate description generation batch_69e3cfaac2b881909e1140339eb1a0dd completed April 18, 2026, 6:38 p.m.
Created at: April 10, 2026, 5:52 a.m.