Triple

T2214079
Position Surface form Disambiguated ID Type / Status
Subject Presbyterian Church of Korea E50982 entity
Predicate scriptureLanguageInWorship P3115 FINISHED
Object Korean Bible translations 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: Korean Bible translations | Statement: [Presbyterian Church of Korea, scriptureLanguageInWorship, Korean Bible translations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: scriptureLanguageInWorship
Context triple: [Presbyterian Church of Korea, scriptureLanguageInWorship, Korean Bible translations]
  • A. scripturalUse
    Indicates that one entity is used as a scriptural reference, source, or basis within the context or content of another entity.
  • B. languageOfWorship chosen
    Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
  • C. hasLanguageOfScripture
    Indicates that an entity’s scriptural or sacred texts are written or expressed in a specified language.
  • D. scripturalTheme
    Indicates that one entity represents a central religious or theological theme expressed, discussed, or emphasized within a scriptural text or passage.
  • E. liturgicalText
    Indicates that one entity is a liturgical or ritual text used in the religious or ceremonial practices associated with 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_69a88b06709c8190978fb2418470d1b6 completed March 4, 2026, 7:41 p.m.
NER Named-entity recognition batch_69abbfef875c8190b642736b4cc11d4c completed March 7, 2026, 6:04 a.m.
PD Predicate disambiguation batch_69abbdaa26d48190860c33fd464c4845 completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:46 p.m.