Triple

T759304
Position Surface form Disambiguated ID Type / Status
Subject MetroAccess E16029 entity
Predicate bookingMethod P1030 FINISHED
Object telephone reservation 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: telephone reservation | Statement: [MetroAccess, bookingMethod, telephone reservation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: bookingMethod
Context triple: [MetroAccess, bookingMethod, telephone reservation]
  • A. 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.
  • B. appointmentMethod chosen
    Indicates how an appointment is arranged, such as the channel, process, or means used to schedule it.
  • C. mainReservation
    Indicates that one reservation is designated as the primary or central booking associated with a person, account, or set of related reservations.
  • D. reservationSystem
    Indicates a system or process that manages the creation, modification, and tracking of reservations or bookings between parties.
  • E. modernReservation
    Indicates that an entity is a contemporary or currently active reservation associated with another entity (such as a group, person, 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_69a493684ee48190bd43b7c78da4aec8 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a67f9778819098d3c144dd26b976 completed March 1, 2026, 8:50 p.m.
PD Predicate disambiguation batch_69a4a50348088190873a1446db657a78 completed March 1, 2026, 8:43 p.m.
Created at: March 1, 2026, 7:37 p.m.