Triple

T31182525
Position Surface form Disambiguated ID Type / Status
Subject GLASGOW CTL & QST E794933 entity
Predicate ticketingTreatment P171224 FINISHED
Object treats member stations as interchangeable for fares 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: treats member stations as interchangeable for fares | Statement: [GLASGOW CTL & QST, ticketingTreatment, treats member stations as interchangeable for fares]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ticketingTreatment
Context triple: [GLASGOW CTL & QST, ticketingTreatment, treats member stations as interchangeable for fares]
  • A. ticketingIssue
    Indicates that there is a problem, error, or complication related to a ticketing process or ticket-based system.
  • B. ticketingContext
    Indicates the situational or operational context in which a ticket (such as a support, event, or issue ticket) is created, managed, or applied.
  • C. ticketingResponsibility
    Indicates responsibility for issuing, managing, or handling tickets within a given context or system.
  • D. ticketingPlan
    Indicates the specific ticketing arrangement, policy, or scheme that governs how tickets are issued, priced, or managed for an event or service.
  • E. ticketingFor
    Indicates that one entity is responsible for issuing, managing, or providing tickets for another entity, such as an event, service, or venue.
  • 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_69f224d675d08190957198068e440422 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69c6f01e881908fa84f5d429d37ae completed May 3, 2026, 12:53 a.m.
PD Predicate disambiguation batch_69f69665cd9c819088c388fc82fec42e completed May 3, 2026, 12:27 a.m.
PDg Predicate description generation batch_69f69c2127088190ae92c72461576d3b completed May 3, 2026, 12:51 a.m.
Created at: April 29, 2026, 9:08 p.m.