Triple

T37839078
Position Surface form Disambiguated ID Type / Status
Subject Chamber Chorus (UC Berkeley) E943420 entity
Predicate auditionRequired P189547 FINISHED
Object yes 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: yes | Statement: [Chamber Chorus (UC Berkeley), auditionRequired, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: auditionRequired
Context triple: [Chamber Chorus (UC Berkeley), auditionRequired, yes]
  • A. auditionedFor
    Indicates that one entity formally tried out or performed in order to be considered for a role, position, or opportunity associated with another entity.
  • B. auditionContext
    Indicates the situational setting or circumstances under which an audition takes place, such as its purpose, format, or conditions.
  • C. audienceRequirement
    Indicates that a certain type or level of audience is required or expected for something (e.g., an event, work, or activity).
  • D. licenceRequiredFor
    Indicates that a specific license is legally or formally required in order to perform, use, access, or operate the related entity or activity.
  • E. hasAcousticsSuitableFor
    Indicates that something possesses acoustic properties that are appropriate or well-suited for a particular use, activity, or environment.
  • 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_69f76eeb0f7081908d6d3adbc469889c completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbc36ce1f88190a7fa1656b714e107 completed May 6, 2026, 10:40 p.m.
PD Predicate disambiguation batch_69fbbd166a488190b1bf9316b0790801 completed May 6, 2026, 10:13 p.m.
PDg Predicate description generation batch_69fbc36bcac48190a726b40442c094d1 completed May 6, 2026, 10:40 p.m.
Created at: May 3, 2026, 4:19 p.m.