Triple

T25784623
Position Surface form Disambiguated ID Type / Status
Subject Rita v. United States E649385 entity
Predicate postBookerCase P159263 FINISHED
Object true 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: true | Statement: [Rita v. United States, postBookerCase, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: postBookerCase
Context triple: [Rita v. United States, postBookerCase, true]
  • 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. headBooker
    Indicates that one entity serves as the primary organizer or decision-maker (e.g., main scheduler or match-maker) for another entity within an event or production context.
  • C. bookingHubFor
    Indicates that one entity serves as the central platform or system through which bookings or reservations are made for another entity.
  • D. hasBooker
    Indicates that one entity serves as the booking agent or person responsible for arranging engagements for another entity.
  • E. bookingDecisionBy
    Indicates that a particular entity (such as a person or system) is responsible for making the decision to create, confirm, modify, or cancel a booking.
  • F. None of above. chosen

Provenance (4 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_69e7ab33e9308190afe415dc6f9e8876 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f5fef935a8819083bc9cefa4a72f8e completed May 2, 2026, 1:41 p.m.
PD Predicate disambiguation batch_69f4938b960081909b53c074a3e0c7c2 completed May 1, 2026, 11:50 a.m.
PDg Predicate description generation batch_69f497b8abb88190bb672cf6907c4b8d completed May 1, 2026, 12:08 p.m.
Created at: April 22, 2026, 5:53 a.m.