Triple

T22878893
Position Surface form Disambiguated ID Type / Status
Subject Sonata I in F major E567401 entity
Predicate usesContrapuntalWriting P99482 FINISHED
Object true 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: true | Statement: [Sonata I in F major, usesContrapuntalWriting, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesContrapuntalWriting
Context triple: [Sonata I in F major, usesContrapuntalWriting, true]
  • A. hasContrapuntalWriting
    Indicates that one musical entity features contrapuntal writing in relation to another, meaning multiple independent melodic lines are combined according to contrapuntal principles.
  • B. usesCantusFirmus
    Indicates that one musical element is based on or incorporates a pre-existing cantus firmus melody as its structural foundation.
  • C. usesChorale
    Indicates that one entity incorporates or employs a chorale (a hymn-like musical piece) within its structure or content.
  • D. usesCounterpoint chosen
    Indicates that one entity employs counterpoint, combining independent melodic lines in a structured, interdependent musical relationship with another.
  • E. usesBassoContinuo
    Indicates that an entity employs or incorporates basso continuo as part of its musical texture or accompaniment.
  • 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_69e24589d8348190b96422d13a678bc1 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17f5a26f4819086ede6d85a2ab2bf completed April 29, 2026, 3:47 a.m.
PD Predicate disambiguation batch_69ef3b6b2e2481908258156937b5a745 completed April 27, 2026, 10:33 a.m.
Created at: April 17, 2026, 3:39 p.m.