Triple

T1970099
Position Surface form Disambiguated ID Type / Status
Subject Peel Hall tram stop E42778 entity
Predicate hasTicketValidation P3383 FINISHED
Object smartcard validators 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: smartcard validators | Statement: [Peel Hall tram stop, hasTicketValidation, smartcard validators]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTicketValidation
Context triple: [Peel Hall tram stop, hasTicketValidation, smartcard validators]
  • A. hasTicketRequirement
    Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
  • B. hasTicketing chosen
    Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
  • C. hasTicketHall
    Indicates that a place or facility includes or is equipped with a designated ticket hall area for purchasing or validating tickets.
  • D. ranOnTicketWith
    Indicates that a candidate or person campaigned or sought office as part of, or associated with, a particular electoral ticket.
  • E. hasPass
    Indicates that an entity possesses or has been granted a pass, such as a ticket, permit, or authorization to access something.
  • 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_69a88711151c8190940b2572095059d7 completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb3d17274819084cd352a3d2a8151 completed March 7, 2026, 5:12 a.m.
PD Predicate disambiguation batch_69abaff7d4a48190ab0d51aefb1c4e31 completed March 7, 2026, 4:56 a.m.
Created at: March 4, 2026, 7:36 p.m.