Triple

T3188200
Position Surface form Disambiguated ID Type / Status
Subject Russian Orthodox Church Outside Russia E66752 entity
Predicate historicallyOpposedTo P437 FINISHED
Object Soviet regime 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: Soviet regime | Statement: [Russian Orthodox Church Outside Russia, historicallyOpposedTo, Soviet regime]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyOpposedTo
Context triple: [Russian Orthodox Church Outside Russia, historicallyOpposedTo, Soviet regime]
  • A. historicallyOpposedBy
    Indicates that one entity has been the target of opposition, resistance, or antagonism from another entity over a historical period.
  • B. emergedInOppositionTo
    Indicates that one entity came into existence or gained prominence specifically as a reaction or counter-movement against another entity.
  • C. historicallyContestedBy
    Indicates that two or more parties have disputed or challenged control, ownership, or interpretation of something over a period of history.
  • D. opposedBy chosen
    Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
  • E. historicallyConsidered
    Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
  • 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_69ad8587c1bc8190a2595f2c22ee1001 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada6e491508190bc881feaee3889bc completed March 8, 2026, 4:42 p.m.
PD Predicate disambiguation batch_69ad9e04290481909092ddfbe6fdaabc completed March 8, 2026, 4:04 p.m.
Created at: March 8, 2026, 3:06 p.m.