Triple

T1672818
Position Surface form Disambiguated ID Type / Status
Subject Diamond Jubilee Concert E36161 entity
Predicate liveAudienceSize P3653 FINISHED
Object approximately 10,000 ticket holders 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: approximately 10,000 ticket holders | Statement: [Diamond Jubilee Concert, liveAudienceSize, approximately 10,000 ticket holders]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: liveAudienceSize
Context triple: [Diamond Jubilee Concert, liveAudienceSize, approximately 10,000 ticket holders]
  • A. audienceSizeApproximate chosen
    Indicates an estimated or approximate number of people in the audience for an event or content.
  • B. hasAudienceSize
    Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
  • C. approximateAudienceSize
    Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
  • D. audienceCapacityType
    Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
  • E. hasAudienceReception
    Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
  • 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_69a8861286808190939afff3ce8ee31e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69ab272a653481908f48aa1eed5de8a4 completed March 6, 2026, 7:12 p.m.
PD Predicate disambiguation batch_69aa61b2f6288190b2348ef7d7e4672d completed March 6, 2026, 5:10 a.m.
Created at: March 4, 2026, 7:29 p.m.