Triple

T9380988
Position Surface form Disambiguated ID Type / Status
Subject SPT Zone 1 E225780 entity
Predicate fareRelevance P65069 FINISHED
Object determines ticket prices within central 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: determines ticket prices within central Glasgow | Statement: [SPT Zone 1, fareRelevance, determines ticket prices within central Glasgow]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fareRelevance
Context triple: [SPT Zone 1, fareRelevance, determines ticket prices within central Glasgow]
  • A. farePolicyRelatedTo chosen
    Indicates a relationship where a fare policy is associated with, applies to, or governs a particular entity, context, or service.
  • B. fareIntegrationScope
    Indicates the extent to which fares are coordinated or unified across different transportation services or systems.
  • C. fare
    Indicates the price or cost required for a person or thing to be transported by a particular mode of travel or service.
  • D. relatedBenefit
    Indicates that one entity provides an advantage, gain, or positive outcome that is connected or attributable to another entity.
  • E. fareAppliesTo
    Indicates that a specific fare is applicable to a particular trip, service, passenger category, or travel condition.
  • 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_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.
Created at: March 30, 2026, 7:44 p.m.