Triple

T38665833
Position Surface form Disambiguated ID Type / Status
Subject II. Allegro appassionato E940450 entity
Predicate hasMainSoloInstrument P193990 FINISHED
Object piano 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: piano | Statement: [II. Allegro appassionato, hasMainSoloInstrument, piano]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMainSoloInstrument
Context triple: [II. Allegro appassionato, hasMainSoloInstrument, piano]
  • A. hasMainInstrumentalElements
    Indicates that one entity includes or is characterized by the primary instrumental components or parts of another entity.
  • B. hasBassSolo
    Indicates that a musical piece, section, or performance includes a solo passage specifically played by the bass instrument.
  • C. hasMajorInstrument chosen
    Indicates that an entity’s primary or main musical instrument is a specified instrument.
  • D. hasNoInstrumentalAccompaniment
    Indicates that an action or event occurs without any instrumental musical accompaniment.
  • E. frequentSoloInstrument
    Indicates that an instrument is commonly used as a solo instrument in performances or compositions.
  • 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_69f76edfde348190bf6529d9f49ecd62 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a037c9141dc819098d7fcc36e69882c completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a2026248190b894436a578d79ac completed May 12, 2026, 7:06 p.m.
Created at: May 3, 2026, 4:33 p.m.