Triple

T22870510
Position Surface form Disambiguated ID Type / Status
Subject Materna E567177 entity
Predicate hasMelodicRange P150052 FINISHED
Object moderate vocal range suitable for congregational singing 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: moderate vocal range suitable for congregational singing | Statement: [Materna, hasMelodicRange, moderate vocal range suitable for congregational singing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMelodicRange
Context triple: [Materna, hasMelodicRange, moderate vocal range suitable for congregational singing]
  • A. hasMoreMelodicSoundThan
    Indicates that the sound produced by one entity is judged to be more melodic, tuneful, or musically pleasing than the sound produced by another entity.
  • B. hasMelody
    Indicates that one entity possesses, contains, or is characterized by a particular melody.
  • C. isMelodic
    Indicates that something possesses a tuneful, harmonious, or musically pleasing quality.
  • D. hasMelodyInstrument
    Indicates that something uses or features a particular instrument to carry the main melody.
  • E. hasMelodicHook
    Indicates that a musical piece contains a distinctive, memorable melodic phrase designed to catch the listener’s attention.
  • 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_69e24589d8348190b96422d13a678bc1 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17f04b06481909004818ec8fc5a26 completed April 29, 2026, 3:46 a.m.
PD Predicate disambiguation batch_69eed2d8c0608190afef4c4e530c0e2c completed April 27, 2026, 3:07 a.m.
PDg Predicate description generation batch_69eeeb577e2081909f4a4e9c296535c0 completed April 27, 2026, 4:51 a.m.
Created at: April 17, 2026, 3:38 p.m.