Triple

T36567341
Position Surface form Disambiguated ID Type / Status
Subject String Quartet No. 5 E902013 entity
Predicate hasTonalityFeature P167001 FINISHED
Object non-traditional tonality 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: non-traditional tonality | Statement: [String Quartet No. 5, hasTonalityFeature, non-traditional tonality]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTonalityFeature
Context triple: [String Quartet No. 5, hasTonalityFeature, non-traditional tonality]
  • A. hasTonalityShift
    Indicates a change in the tonal quality, mood, or key within a piece or segment, marking a shift from one tonality to another.
  • B. inTonality
    Indicates that something (such as a musical element, passage, or piece) is expressed, structured, or interpreted within a specific musical key or tonal framework.
  • C. hasPhonemicTone
    Indicates that a language, word, or syllable uses pitch differences (tones) as phonemic contrasts that can change meaning.
  • D. tonalFeatures chosen
    Indicates that one entity specifies or characterizes the tonal properties or qualities associated with another entity.
  • E. tonalCharacteristic
    Indicates the specific quality or character of a sound’s tone, such as its color, texture, or expressive nuance, in relation to an entity.
  • 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_69f76e6416708190a9754b8c52d4e453 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fd64bc86848190a49f451a8fc5cf1e completed May 8, 2026, 4:21 a.m.
PD Predicate disambiguation batch_69fd5ff4a648819090756d90fd195d9a completed May 8, 2026, 4 a.m.
Created at: May 3, 2026, 4:11 p.m.