Triple

T485445
Position Surface form Disambiguated ID Type / Status
Subject Northern Trains E9865 entity
Predicate acceptsTicketType P8859 FINISHED
Object rail season tickets 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: rail season tickets | Statement: [Northern Trains, acceptsTicketType, rail season tickets]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: acceptsTicketType
Context triple: [Northern Trains, acceptsTicketType, rail season tickets]
  • A. ticketingCompatibleWith
    Indicates that two systems, services, or components can interoperate or be used together within the same ticketing or reservation workflow without conflict.
  • B. hasTicketing
    Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
  • C. hasTicketRequirement
    Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
  • D. fareType
    Indicates the category or class of fare (such as standard, discounted, or promotional) that applies to a given trip, ticket, or pricing instance.
  • E. fareTypes chosen
    Indicates the categories or kinds of fares (e.g., ticket or pricing options) that apply to a given travel or service offering.
  • 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_69a2e802e2908190ab17c9479e0b6412 completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2f0bb46788190b40182bf2a54f98f completed Feb. 28, 2026, 1:42 p.m.
PD Predicate disambiguation batch_69a2edf48ec08190b85d07e194f99c49 completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.