Triple

T24287215
Position Surface form Disambiguated ID Type / Status
Subject Sunbury railway station E605702 entity
Predicate hasMykiTicketing P41459 FINISHED
Object yes 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: yes | Statement: [Sunbury railway station, hasMykiTicketing, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMykiTicketing
Context triple: [Sunbury railway station, hasMykiTicketing, yes]
  • A. hasTicketInspection
    Indicates that a ticket is checked or verified by an authorized inspector or system.
  • B. hasTicketing
    Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
  • C. hasTicketAccess
    Indicates that an entity is permitted to view, use, or manage a particular ticket or set of tickets.
  • D. hasElectronicTicketing chosen
    Indicates that an entity supports or provides electronic ticketing for access, booking, or transactions.
  • E. isWithinFareSystem
    Indicates that one transportation service, route, or area operates under and is covered by a specified fare or ticketing system.
  • 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_69e295480d0c8190846fc3c2e2da1d4c completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f28f56cdc08190a1e06f67dffd4769 completed April 29, 2026, 11:08 p.m.
PD Predicate disambiguation batch_69f1c457a2908190993824395b3c365d completed April 29, 2026, 8:41 a.m.
Created at: April 18, 2026, 12:08 a.m.