Triple

T29029084
Position Surface form Disambiguated ID Type / Status
Subject Introduzione: Un poco adagio – Allegro vivace E737676 entity
Predicate premierInstrument P99288 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: [Introduzione: Un poco adagio – Allegro vivace, premierInstrument, piano]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: premierInstrument
Context triple: [Introduzione: Un poco adagio – Allegro vivace, premierInstrument, piano]
  • A. typicalInstrumentAtPremiere chosen
    Indicates that a particular musical instrument is commonly used or featured during the premiere performance of a work.
  • B. primaryInstrumentAbbreviation
    Indicates that one entity is the standard shortened or abbreviated form of the name of another entity’s primary instrument.
  • C. parentInstrument
    Indicates that one instrument serves as the broader, containing, or originating instrument from which another, more specific or derived instrument is related.
  • D. premiereOrganist
    Indicates that an entity serves as the primary or leading organist in a particular context, event, or organization.
  • E. introducedInstrument
    Indicates that one entity caused or brought about the initial use or adoption of a particular instrument by another entity or within a given context.
  • 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_69f077ef00fc81909325f084ad37c035 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69f69383222c81909d8baa04129d5c81 completed May 3, 2026, 12:14 a.m.
PD Predicate disambiguation batch_69f690eb1e948190aab41a89969519a5 completed May 3, 2026, 12:03 a.m.
Created at: April 28, 2026, 9:54 a.m.