Triple

T8469349
Position Surface form Disambiguated ID Type / Status
Subject Piano Trio in G minor, Op. 17 E200241 entity
Predicate hasFinaleMovement P83468 FINISHED
Object Allegretto 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: Allegretto | Statement: [Piano Trio in G minor, Op. 17, hasFinaleMovement, Allegretto]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFinaleMovement
Context triple: [Piano Trio in G minor, Op. 17, hasFinaleMovement, Allegretto]
  • A. hasFinishingMove
    Indicates that one entity possesses or is associated with a specific, often decisive or signature, final action or move used to conclude an encounter or event.
  • B. laterFinale
    Indicates that one event, episode, or occurrence serves as a concluding part that happens after another referenced event or finale.
  • C. finalAct
    Indicates that an action or event is the last or concluding act in a sequence or process.
  • D. hasUnfinishedEnding
    Indicates that an entity concludes in an incomplete, unresolved, or open-ended manner rather than reaching a fully finished state.
  • E. finalMovementKey
    Indicates that one movement in a sequence is designated as the last or concluding movement, often used as a key or reference to the final step in a process or animation.
  • F. None of above. chosen

Provenance (4 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_69ca831a4f348190bfdd09250e86ae35 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe4d5dd088190a79050417f527f14 completed March 31, 2026, 3:14 p.m.
PD Predicate disambiguation batch_69cbd10072cc819084be1ed9ac7ebe9d completed March 31, 2026, 1:49 p.m.
PDg Predicate description generation batch_69cbe30c2d088190b4cb89adb4e88273 completed March 31, 2026, 3:06 p.m.
Created at: March 30, 2026, 6:11 p.m.