Triple

T5391128
Position Surface form Disambiguated ID Type / Status
Subject Monterey–San Jose Thruway Motorcoach E120330 entity
Predicate ticketPurchase P34227 FINISHED
Object available via Amtrak sales channels 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: available via Amtrak sales channels | Statement: [Monterey–San Jose Thruway Motorcoach, ticketPurchase, available via Amtrak sales channels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ticketPurchase
Context triple: [Monterey–San Jose Thruway Motorcoach, ticketPurchase, available via Amtrak sales channels]
  • A. ticketingProduct
    Indicates a relationship where an entity is associated with, or offered as, a ticketing-related product (such as a service or item used for issuing, managing, or selling tickets).
  • B. ticketDemand
    Indicates that there is a level of desire or need among potential buyers for tickets to an event, service, or offering.
  • C. ticketPurchaseMethod chosen
    Indicates the method or channel through which a ticket was purchased (e.g., online, in person, via mobile app).
  • D. ticket
    Indicates that an entity serves as or is associated with a ticket, typically representing authorization, access, or a record for an event, service, or transaction.
  • E. ticketMachines
    Indicates that there is a relationship involving ticket machines, typically denoting where they are located, available, or associated with a particular entity or place.
  • 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_69bd46354c648190a38b26f107010a96 completed March 20, 2026, 1:05 p.m.
NER Named-entity recognition batch_69bd87185f788190bd5244a1f7dbb5c8 completed March 20, 2026, 5:42 p.m.
PD Predicate disambiguation batch_69bd8463a9c88190bd760378f3026180 completed March 20, 2026, 5:31 p.m.
Created at: March 20, 2026, 2:04 p.m.