Triple

T9520686
Position Surface form Disambiguated ID Type / Status
Subject Symphony No. 2 in C minor, Op. 17 E229635 entity
Predicate usesFolkMelodies P85135 FINISHED
Object Ukrainian folk songs 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: Ukrainian folk songs | Statement: [Symphony No. 2 in C minor, Op. 17, usesFolkMelodies, Ukrainian folk songs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesFolkMelodies
Context triple: [Symphony No. 2 in C minor, Op. 17, usesFolkMelodies, Ukrainian folk songs]
  • A. usesFolkMaterial chosen
    Indicates that one entity incorporates or draws upon traditional folk materials, such as melodies, stories, or motifs, in relation to another entity.
  • B. includesTraditionalSong
    Indicates that one entity contains or features a traditional song as part of its content or composition.
  • C. melodyReusedBy
    Indicates that a melody originally used in one work is later reused or incorporated in another work.
  • D. isTraditionallySungBy
    Indicates that something, typically a song or chant, is customarily performed vocally by a particular person, group, or type of performer according to tradition.
  • E. hasMelody
    Indicates that one entity possesses, contains, or is characterized by a particular melody.
  • 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_69ca847870a881909d8d751a7d29da39 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9884dd5c8190b69c178cb2ac75c2 completed April 1, 2026, 10:13 p.m.
PD Predicate disambiguation batch_69cca56a3d088190bdc16670678fb6c6 completed April 1, 2026, 4:56 a.m.
Created at: March 30, 2026, 7:59 p.m.