Triple

T9380964
Position Surface form Disambiguated ID Type / Status
Subject Glasgow Central and Queen Street E225779 entity
Predicate routeingPointFor P88625 FINISHED
Object long‑distance rail journeys to and from Glasgow 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: long‑distance rail journeys to and from Glasgow | Statement: [Glasgow Central and Queen Street, routeingPointFor, long‑distance rail journeys to and from Glasgow]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: routeingPointFor
Context triple: [Glasgow Central and Queen Street, routeingPointFor, long‑distance rail journeys to and from Glasgow]
  • A. locatedOnRouteTo
    Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
  • B. routesFrom
    Indicates that something (such as a path, connection, or communication) originates at one entity and is directed or carried from that source entity toward another.
  • C. approachRoute
    Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
  • D. routeBetween
    Indicates that there exists a path or connection enabling travel or communication between two locations or points.
  • E. routeOptimization
    Indicates the process of determining the most efficient path or sequence of paths between locations according to specified criteria such as distance, time, or cost.
  • 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_69ca842e9dcc8190a264119e683cfe04 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd50bc94108190a1b8146a78166009 completed April 1, 2026, 5:07 p.m.
PD Predicate disambiguation batch_69cca53bd6ec81909bf403ce304e5c08 completed April 1, 2026, 4:55 a.m.
PDg Predicate description generation batch_69cca89b3368819087a3d69270c1f185 completed April 1, 2026, 5:09 a.m.
Created at: March 30, 2026, 7:44 p.m.