Triple

T3010044
Position Surface form Disambiguated ID Type / Status
Subject Heaton Park Metrolink stop E82193 entity
Predicate servesTramSystem P17788 FINISHED
Object light rail 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: light rail | Statement: [Heaton Park Metrolink stop, servesTramSystem, light rail]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servesTramSystem
Context triple: [Heaton Park Metrolink stop, servesTramSystem, light rail]
  • A. hasTramway chosen
    Indicates that a location or area is served by, contains, or is connected to a tramway system.
  • B. partOfTransitSystem
    Indicates that something is a component or segment within a larger transit or transportation system.
  • C. rapidTransitSystem
    Indicates a transportation relationship where people or goods are moved via a high-capacity, high-frequency public transit system designed for rapid travel over urban or regional routes.
  • D. appliesToTransitSystem
    Indicates that something (such as a rule, policy, feature, or condition) is relevant or applicable to a particular transit or transportation system.
  • E. transportationServedBy
    Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
  • 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_69ad8b1eb53481908c39bbcd1ec104b2 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9a4ccbf08190a7580c9e758804d0 completed March 8, 2026, 3:48 p.m.
PD Predicate disambiguation batch_69ad96180eb08190a524c5f458d41382 completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 3 p.m.