Triple

T2502465
Position Surface form Disambiguated ID Type / Status
Subject BBC Proms E52494 entity
Predicate ticketingFeature P36295 FINISHED
Object low-priced standing tickets 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: low-priced standing tickets | Statement: [BBC Proms, ticketingFeature, low-priced standing tickets]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ticketingFeature
Context triple: [BBC Proms, ticketingFeature, low-priced standing tickets]
  • A. ticketingCompatibleWith
    Indicates that two systems, services, or components can interoperate or be used together within the same ticketing or reservation workflow without conflict.
  • B. hasTicketing
    Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
  • C. ticketingProduct chosen
    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).
  • D. ticketDemand
    Indicates that there is a level of desire or need among potential buyers for tickets to an event, service, or offering.
  • E. ticketedAttraction
    Indicates that access to the attraction requires a purchased ticket or paid admission.
  • 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_69ab4957b3a88190adf968ae0c1b931c completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abd1c9f80c8190b40ada396e184e75 completed March 7, 2026, 7:20 a.m.
PD Predicate disambiguation batch_69abd0bba5348190bb4637d3165cb339 completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:46 p.m.