Triple

T28299087
Position Surface form Disambiguated ID Type / Status
Subject La Voce E713654 entity
Predicate hasPerformerVoiceType P135747 FINISHED
Object tenor 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: tenor | Statement: [La Voce, hasPerformerVoiceType, tenor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPerformerVoiceType
Context triple: [La Voce, hasPerformerVoiceType, tenor]
  • A. hasMusicalVocalType chosen
    Indicates that an entity is associated with a specific type or classification of singing voice.
  • B. hasVocalAdaptationPerformer
    Indicates that a performer possesses or employs a specific vocal adaptation or modification in their performance.
  • C. hasNotableVocalType
    Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
  • D. hasVocalPerformanceBy
    Indicates that a vocal performance in a work or recording is performed by a specified person or group.
  • 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_69efb524ab688190a1ce7ee7c9520932 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69f760a35b988190904e6267553ad2fe completed May 3, 2026, 2:50 p.m.
PD Predicate disambiguation batch_69f75eb3d6f081908c933474eb359e3d completed May 3, 2026, 2:41 p.m.
Created at: April 27, 2026, 11:34 p.m.