Triple

T19809567
Position Surface form Disambiguated ID Type / Status
Subject Adonai E475905 entity
Predicate avoidsPronunciationOf P137401 FINISHED
Object divine name YHWH 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: divine name YHWH | Statement: [Adonai, avoidsPronunciationOf, divine name YHWH]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: avoidsPronunciationOf
Context triple: [Adonai, avoidsPronunciationOf, divine name YHWH]
  • A. correctPronunciation
    Indicates that one entity provides the accurate or standard way to pronounce another entity (such as a word or name).
  • B. cannotBeEasilySpokenBy
    Indicates that one entity (typically a word, phrase, or name) is difficult for another entity (typically a speaker or group) to pronounce or articulate smoothly.
  • C. hasPronunciationDifferenceFrom
    Indicates that two linguistic items differ in how they are pronounced.
  • D. isMorePronouncedIn
    Indicates that a particular feature, quality, or effect appears with greater intensity or prominence in one context, entity, or condition than in another.
  • E. typeOfPronunciationDescribed
    Indicates that one entity specifies or characterizes the kind or style of pronunciation associated with another entity.
  • F. None of above. chosen

Provenance (4 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_69d8e51bc4208190a1c57d8c5d1b15e4 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6542ac1b48190a0cb69dbceca74da completed April 20, 2026, 4:28 p.m.
PD Predicate disambiguation batch_69e5305858108190bbbfdb9ba3ab9f80 completed April 19, 2026, 7:43 p.m.
PDg Predicate description generation batch_69e532bcf41c8190b685b5adf46a60fc completed April 19, 2026, 7:53 p.m.
Created at: April 10, 2026, 1:50 p.m.