Triple

T11966296
Position Surface form Disambiguated ID Type / Status
Subject Choral Symphony E284796 entity
Predicate hasFinalMovementType P83468 FINISHED
Object choral finale 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: choral finale | Statement: [Choral Symphony, hasFinalMovementType, choral finale]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFinalMovementType
Context triple: [Choral Symphony, hasFinalMovementType, choral finale]
  • A. hasFinaleMovement chosen
    Indicates that one entity (typically a musical work or performance) includes another entity as its concluding or final movement.
  • B. hasMovementType
    Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
  • C. formOfFinalMovement
    Indicates that one movement serves as the concluding or final section of another movement or larger musical work.
  • D. 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.
  • 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.

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_69d6ab2eaeb881909f7914758f859413 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9037adf5881908abe1a4e64a71f20 completed April 10, 2026, 2:04 p.m.
PD Predicate disambiguation batch_69d8bb40f30c8190a0e0719bd67542bf completed April 10, 2026, 8:56 a.m.
Created at: April 8, 2026, 9:46 p.m.