Triple

T30191526
Position Surface form Disambiguated ID Type / Status
Subject Carolyn McCormick E767497 entity
Predicate hasVoiceWork P18510 FINISHED
Object audiobook narration 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: audiobook narration | Statement: [Carolyn McCormick, hasVoiceWork, audiobook narration]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVoiceWork
Context triple: [Carolyn McCormick, hasVoiceWork, audiobook narration]
  • A. hasVoiceIn
    Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
  • B. hasVoices
    Indicates that an entity possesses or includes one or more vocal parts, voice tracks, or spoken/sung voice elements.
  • C. hasVoiceActing
    Indicates that one entity provides voice performance for a character, role, or work associated with another entity.
  • D. voiceWork chosen
    Indicates that one entity performs or contributes voice acting or vocal performance work for another entity or creative production.
  • E. hasVoicing
    Indicates that one sound, segment, or phoneme is characterized by the presence or absence of vocal fold vibration (voicing) in relation to another or to a specified voicing property.
  • 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_69f2247cc3d88190811dec3face94bf5 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6fb19063c81909466b329655c8583 completed May 3, 2026, 7:36 a.m.
PD Predicate disambiguation batch_69f6f969b4cc8190afb473a2d8b110bc completed May 3, 2026, 7:29 a.m.
Created at: April 29, 2026, 7:28 p.m.