Triple

T7424386
Position Surface form Disambiguated ID Type / Status
Subject Defying Gravity E171330 entity
Predicate requiresVocalRange P40358 FINISHED
Object high belt for female voice 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: high belt for female voice | Statement: [Defying Gravity, requiresVocalRange, high belt for female voice]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresVocalRange
Context triple: [Defying Gravity, requiresVocalRange, high belt for female voice]
  • A. vocalRange
    Indicates the span of pitches or notes that an entity (such as a singer or instrument) is capable of producing.
  • B. hasVocalRangeDescription
    Indicates that an entity is associated with a textual description of its vocal range or vocal capabilities.
  • C. vocalRequirement chosen
    Indicates that a particular action, role, or participation involves a specified need or condition related to vocal use, such as speaking or singing.
  • D. hasNotableVocalType
    Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
  • E. isVocalShowcaseFor
    Indicates that something serves as a performance or context specifically designed to highlight and display another entity’s vocal abilities.
  • 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_69c68a625d048190af70eb8b63bec5a0 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f302b33481908eae877970f2bbdf completed March 27, 2026, 9:13 p.m.
PD Predicate disambiguation batch_69c6f03648d08190b862d07fef71210c completed March 27, 2026, 9:01 p.m.
Created at: March 27, 2026, 3:12 p.m.