Triple

T14261070
Position Surface form Disambiguated ID Type / Status
Subject SacRT SmaRT Ride E353516 entity
Predicate bookingTime P80081 FINISHED
Object advance booking allowed 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: advance booking allowed | Statement: [SacRT SmaRT Ride, bookingTime, advance booking allowed]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: bookingTime
Context triple: [SacRT SmaRT Ride, bookingTime, advance booking allowed]
  • A. bookingModel
    Indicates a relationship where an entity uses or is associated with a specific model or schema that defines how bookings are structured, processed, or represented.
  • B. bookingHubFor
    Indicates that one entity serves as the central platform or system through which bookings or reservations are made for another entity.
  • C. bookingWindow chosen
    Indicates the time period before an event or service during which a booking or reservation can be made.
  • D. bookingOption
    Indicates a selectable arrangement or choice available for making a booking, such as a specific time, package, or set of conditions under which a reservation can be made.
  • E. bookingPattern
    Indicates a recurring or characteristic way in which bookings are made, such as their timing, frequency, or sequence.
  • 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_69d8278c43e08190824146f4632b89a5 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de635534988190816fdfb315cd2a3f completed April 14, 2026, 3:55 p.m.
PD Predicate disambiguation batch_69de2a7d586c8190846ff242bbf5ac53 completed April 14, 2026, 11:52 a.m.
Created at: April 10, 2026, 1:09 a.m.