Triple

T36406612
Position Surface form Disambiguated ID Type / Status
Subject Церковь Святого Архангела Михаила E896763 entity
Predicate имеет культовую функцию P47658 FINISHED
Object место молитвы 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: место молитвы | Statement: [Церковь Святого Архангела Михаила, имеет культовую функцию, место молитвы]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: имеет культовую функцию
Context triple: [Церковь Святого Архангела Михаила, имеет культовую функцию, место молитвы]
  • A. hasCulturalFunction
    Indicates that something serves a particular role, purpose, or function within a culture or cultural context.
  • B. hasCulturalCenterFunction
    Indicates that something serves the role or performs the activities of a cultural center, such as hosting cultural events, programs, or services.
  • C. hasCulturalRole
    Indicates that an entity fulfills or is assigned a specific function, position, or significance within a cultural, social, or traditional context.
  • D. hasCultFeature
    Indicates that an entity possesses a characteristic, attribute, or element associated with cultic or ritual practices.
  • E. hasSacredFunction chosen
    Indicates that something serves a religious or holy role, purpose, or duty within a sacred context.
  • 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_69f76e53b81081908d3b81860593f38a completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fbad1e94988190b86d447a68e65067 completed May 6, 2026, 9:05 p.m.
PD Predicate disambiguation batch_69fba881b8e0819094790935152b99a1 completed May 6, 2026, 8:45 p.m.
Created at: May 3, 2026, 4:10 p.m.