Triple

T31434017
Position Surface form Disambiguated ID Type / Status
Subject MWV A 14 E801873 entity
Predicate appliesToVocalForces P62769 FINISHED
Object soloists, choir and orchestra 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: soloists, choir and orchestra | Statement: [MWV A 14, appliesToVocalForces, soloists, choir and orchestra]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appliesToVocalForces
Context triple: [MWV A 14, appliesToVocalForces, soloists, choir and orchestra]
  • A. hasVocalForces chosen
    Indicates that an entity involves or employs vocal performers or vocal parts as a contributing force.
  • B. vocalForces
    Indicates a relationship where one entity uses vocal expression (such as speech, singing, or sound) to exert influence, pressure, or compulsion on another entity.
  • C. vocalEffects
    Indicates that one entity applies or produces specific modifications, enhancements, or stylistic effects on another entity’s vocal sound or performance.
  • D. vocalComponent
    Indicates that one entity functions as a vocal or sung component within, or contributing to, another entity (such as a work, performance, or recording).
  • E. featuresVocal
    Indicates that one entity includes or presents the vocal performance or voice of another 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_69f348c475348190bf579ca858eec77c completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69fe38be079c8190a240191ac0e73e3a completed May 8, 2026, 7:25 p.m.
PD Predicate disambiguation batch_69fe350344508190930de2218156ca02 completed May 8, 2026, 7:09 p.m.
Created at: April 30, 2026, 9 p.m.