Triple

T1739793
Position Surface form Disambiguated ID Type / Status
Subject Assyrian Church of the East E38206 entity
Predicate otherLiturgicalLanguage P12203 FINISHED
Object Modern Assyrian (Sureth) 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: Modern Assyrian (Sureth) | Statement: [Assyrian Church of the East, otherLiturgicalLanguage, Modern Assyrian (Sureth)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: otherLiturgicalLanguage
Context triple: [Assyrian Church of the East, otherLiturgicalLanguage, Modern Assyrian (Sureth)]
  • A. usesPrimaryLiturgicalLanguageHistorically
    Indicates that an entity has historically used a particular primary liturgical language in its religious rites or worship practices.
  • B. otherLanguage chosen
    Indicates that an entity has or uses an additional language distinct from its primary or main language.
  • C. isScheduledLanguageOf
    Indicates that a particular language is officially planned or designated to be used for a specific event, program, or context.
  • D. languageOfWorship
    Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
  • 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_69a8862b01a48190ab47209063af82d9 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69ab3c2559ac8190905186406fcaccb9 completed March 6, 2026, 8:42 p.m.
PD Predicate disambiguation batch_69aa61c4023c819099cbe439aefda71f completed March 6, 2026, 5:10 a.m.
Created at: March 4, 2026, 7:30 p.m.