Triple

T31513222
Position Surface form Disambiguated ID Type / Status
Subject Jewish Publication Society E803995 entity
Predicate hasTranslationApproach P198170 FINISHED
Object scholarly 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: scholarly | Statement: [Jewish Publication Society, hasTranslationApproach, scholarly]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTranslationApproach
Context triple: [Jewish Publication Society, hasTranslationApproach, scholarly]
  • A. hasTranslation
    Indicates that one entity is a translation or translated version of another entity in a different language.
  • B. hasTraditionalTranslation
    Indicates that one entity serves as the established or customary translation of another entity in a traditional or historically accepted sense.
  • C. hasTranslated
    Indicates that one entity has rendered the content of another entity from one language into a different language.
  • D. hasTranslationPlatform
    Indicates that one entity provides or is associated with a platform used to perform or manage translations for another entity.
  • E. canTranslateBetween
    Indicates that an entity has the ability to translate or convert information accurately between two specified languages, formats, or representation systems.
  • 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_69f348ceb0a48190ae7feca263b6296c completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69feced53a7c819098ec474fb7d514b0 completed May 9, 2026, 6:06 a.m.
PD Predicate disambiguation batch_69fecd9cd5288190aac8b4e04a7ee78e completed May 9, 2026, 6:01 a.m.
PDg Predicate description generation batch_69feced436a48190b761db7df2d6b6bd completed May 9, 2026, 6:06 a.m.
Created at: April 30, 2026, 9:51 p.m.