Triple

T5997945
Position Surface form Disambiguated ID Type / Status
Subject St. Sava Temple E133518 entity
Predicate secondaryLanguageOfLiturgy P3115 FINISHED
Object Serbian 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: Serbian | Statement: [St. Sava Temple, secondaryLanguageOfLiturgy, Serbian]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: secondaryLanguageOfLiturgy
Context triple: [St. Sava Temple, secondaryLanguageOfLiturgy, Serbian]
  • A. liturgicalLanguageVersion
    Indicates that one entity is a specific version or form of another entity expressed in a particular liturgical language.
  • B. hasSecondaryLiturgy
    Indicates that an entity is associated with an additional, subordinate liturgical service or rite beyond its primary liturgy.
  • C. usesPrimaryLiturgicalLanguageHistorically
    Indicates that an entity has historically used a particular primary liturgical language in its religious rites or worship practices.
  • D. languageOfWorship chosen
    Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
  • E. laterSecondaryLanguageOfAdministration
    Indicates that one language served as a subsequent or later secondary language used for administrative purposes in relation to another language.
  • 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_69c00870ddbc81909880fa3864f4f38d completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04ee274e08190b6478c7ae318ae48 completed March 22, 2026, 8:19 p.m.
PD Predicate disambiguation batch_69c049e152e88190979ab80cb9b50321 completed March 22, 2026, 7:58 p.m.
Created at: March 22, 2026, 4:05 p.m.