Triple

T26567651
Position Surface form Disambiguated ID Type / Status
Subject Koszalin Philharmonic E666731 entity
Predicate focusesOnRepertoire P3738 FINISHED
Object Polish composers 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: Polish composers | Statement: [Koszalin Philharmonic, focusesOnRepertoire, Polish composers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: focusesOnRepertoire
Context triple: [Koszalin Philharmonic, focusesOnRepertoire, Polish composers]
  • A. repertoireIncludes chosen
    Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
  • B. notabilityInRepertoire
    Indicates that a work holds particular significance or prominence within an entity’s repertoire.
  • C. repertoireSource
    Indicates that one entity serves as the origin or provider of the material, content, or items that make up another entity’s repertoire.
  • D. primaryRepertoirePeriod
    Indicates the time period during which an entity’s main or most characteristic repertoire was created, performed, or predominantly active.
  • E. includedInStandardRepertoire
    Indicates that something is part of the commonly accepted or regularly used set within a particular standard repertoire.
  • 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_69ee9cfa21c081909e4e36e087debfc6 completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f6a8df16a88190a23820e64a3b1f92 completed May 3, 2026, 1:46 a.m.
PD Predicate disambiguation batch_69f6a751d5e48190a77dcecbe7ef9f0b completed May 3, 2026, 1:39 a.m.
Created at: April 27, 2026, 1:56 a.m.