Triple

T26337836
Position Surface form Disambiguated ID Type / Status
Subject Enten – Eller E662565 entity
Predicate containsPseudonymousVoice P70072 FINISHED
Object A 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: A | Statement: [Enten – Eller, containsPseudonymousVoice, A]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: containsPseudonymousVoice
Context triple: [Enten – Eller, containsPseudonymousVoice, A]
  • 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. pseudonymousAttribution chosen
    Indicates that an action, work, or statement is attributed to an entity using a pseudonym rather than their real identity.
  • D. hasInnerVoice
    Indicates that an entity possesses an internal monologue or subjective stream of thoughts not externally expressed.
  • E. wasKeyVoiceIn
    Indicates that an entity played a significant or influential role in expressing, shaping, or representing the views or direction of another entity, group, or initiative.
  • 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_69ee81304194819092e20e0fae3aee07 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f7979a073881909a4fde2558e6b6f3 completed May 3, 2026, 6:44 p.m.
PD Predicate disambiguation batch_69f7961550f88190b7bb8a9155458b54 completed May 3, 2026, 6:38 p.m.
Created at: April 26, 2026, 10:37 p.m.