Triple

T332514
Position Surface form Disambiguated ID Type / Status
Subject 1932 Summer Olympics E6654 entity
Predicate ticketPricingPolicy P5429 FINISHED
Object reduced prices due to economic hardship 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: reduced prices due to economic hardship | Statement: [1932 Summer Olympics, ticketPricingPolicy, reduced prices due to economic hardship]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ticketPricingPolicy
Context triple: [1932 Summer Olympics, ticketPricingPolicy, reduced prices due to economic hardship]
  • A. pricingStrategy
    Indicates the approach or method used to set, adjust, or structure prices for products or services in a given context.
  • B. hasTicketing
    Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
  • C. seatSelectionPolicy
    Indicates the rules or constraints governing how seats are chosen or assigned in a given context.
  • D. ticketingCompatibleWith
    Indicates that two systems, services, or components can interoperate or be used together within the same ticketing or reservation workflow without conflict.
  • E. fareDiscount chosen
    Indicates that a reduced price is applied to a standard fare for a product or service.
  • 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_69a2e79434908190a9d5afe415153ad9 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2eab1a7048190ac690ddc2e294914 completed Feb. 28, 2026, 1:16 p.m.
PD Predicate disambiguation batch_69a2e94d99cc8190a112e4b630ec63c1 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.