Triple

T11753341
Position Surface form Disambiguated ID Type / Status
Subject Cavatina: Adagio molto espressivo E279460 entity
Predicate expressiveMarking P70301 FINISHED
Object molto espressivo 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: molto espressivo | Statement: [Cavatina: Adagio molto espressivo, expressiveMarking, molto espressivo]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: expressiveMarking
Context triple: [Cavatina: Adagio molto espressivo, expressiveMarking, molto espressivo]
  • A. expressiveQuality chosen
    Indicates the distinctive emotional or stylistic character conveyed by something, such as how it feels, sounds, or appears in an expressive sense.
  • B. musicalSymbol
    Indicates that one entity is a musical notation mark or sign associated with another entity in a musical context.
  • C. movement3TempoMarking
    Indicates the tempo marking associated specifically with the third movement of a musical work.
  • D. expressivePower
    Indicates the degree to which one system, language, or formalism can represent or capture the behaviors, structures, or concepts expressible in another.
  • E. distinctiveMarking
    Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
  • 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_69d6ab01038c819080714901502c84fc completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a50b8a14819092a7397d73f0a8e3 completed April 10, 2026, 7:21 a.m.
PD Predicate disambiguation batch_69d88a813cc48190a3dfdc60e8af80ae completed April 10, 2026, 5:28 a.m.
Created at: April 8, 2026, 9:41 p.m.