Triple

T31299006
Position Surface form Disambiguated ID Type / Status
Subject Sister Fate E798159 entity
Predicate hasVocalStyleCharacteristic P29850 FINISHED
Object energetic vocals 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: energetic vocals | Statement: [Sister Fate, hasVocalStyleCharacteristic, energetic vocals]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVocalStyleCharacteristic
Context triple: [Sister Fate, hasVocalStyleCharacteristic, energetic vocals]
  • A. hasVocalStyleComparedTo
    Indicates a comparison between entities based on the similarity or resemblance of their vocal style.
  • B. hasHookVocalStyle
    Indicates that an entity (typically a musical work or performance) features a distinctive, catchy vocal delivery or refrain intended to serve as a memorable hook.
  • C. vocalizationCharacteristic chosen
    Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
  • D. hasSecondaryVocalStyle
    Indicates that an entity (typically a performer or recording) employs an additional, non-primary vocal style alongside its main vocal style.
  • E. hasMusicalVocalType
    Indicates that an entity is associated with a specific type or classification of singing voice.
  • 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_69f224e0bd4c8190aab9b29a73f7aa3c completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f727afd5d88190ad48735cd1b32787 completed May 3, 2026, 10:47 a.m.
PD Predicate disambiguation batch_69f72737c42c8190a3f781a5e98868ff completed May 3, 2026, 10:45 a.m.
Created at: April 29, 2026, 9:14 p.m.