Triple

T12164083
Position Surface form Disambiguated ID Type / Status
Subject Travelcard Zone 5 E289783 entity
Predicate hasTicketValidity P47115 FINISHED
Object unlimited travel within covered zones for Travelcards 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: unlimited travel within covered zones for Travelcards | Statement: [Travelcard Zone 5, hasTicketValidity, unlimited travel within covered zones for Travelcards]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTicketValidity
Context triple: [Travelcard Zone 5, hasTicketValidity, unlimited travel within covered zones for Travelcards]
  • A. hasTicketAccess
    Indicates that an entity is permitted to view, use, or manage a particular ticket or set of tickets.
  • B. ticketValidityCovers chosen
    Indicates that the validity period or scope of a ticket extends to and includes a specified time, location, service, or condition.
  • C. hasTicketInspection
    Indicates that a ticket is checked or verified by an authorized inspector or system.
  • D. hasTicketRequirement
    Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
  • E. hasValidityPeriod
    Indicates that something is associated with a specific time span during which it is considered valid or in effect.
  • 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_69d6ab4d6c00819095a9a7c35de83cfb completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d915d7109481908bf5fe512bba3c89 completed April 10, 2026, 3:23 p.m.
PD Predicate disambiguation batch_69d9150c18148190bf8152189c0e5fca completed April 10, 2026, 3:19 p.m.
Created at: April 8, 2026, 9:50 p.m.