Triple

T17854889
Position Surface form Disambiguated ID Type / Status
Subject Principality of Turov E445904 entity
Predicate religiousInstitution P45 FINISHED
Object Orthodox bishopric of Turov NE NERFINISHED

How this triple was built (3 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: Orthodox bishopric of Turov | Statement: [Principality of Turov, religiousInstitution, Orthodox bishopric of Turov]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Orthodox bishopric of Turov
Context triple: [Principality of Turov, religiousInstitution, Orthodox bishopric of Turov]
  • A. Smolensk bishopric
    The Smolensk bishopric was a medieval Eastern Orthodox ecclesiastical see centered in the city of Smolensk, playing a key religious and political role in the region’s history.
  • B. Minsk Eparchy
    The Minsk Eparchy is a key diocesan jurisdiction of the Belarusian Orthodox Church, centered in the capital city of Minsk and overseeing local parishes and religious activities in the region.
  • C. Orthodox bishopric of Chełm
    The Orthodox bishopric of Chełm was a historical Eastern Orthodox ecclesiastical jurisdiction centered in the Chełm (Kholm) region, overseeing the spiritual life of local Orthodox Christian communities.
  • D. Smolensk Eparchy
    Smolensk Eparchy is an ecclesiastical jurisdiction of the Russian Orthodox Church centered in the Smolensk region of western Russia.
  • E. Yaroslavl and Rostov Eparchy
    The Yaroslavl and Rostov Eparchy is a diocese of the Russian Orthodox Church centered in the historic cities of Yaroslavl and Rostov, overseeing numerous parishes, monasteries, and cathedrals in the region.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Orthodox bishopric of Turov
Target entity description: The Orthodox bishopric of Turov was a medieval Eastern Orthodox ecclesiastical see centered in the town of Turov, serving as a major religious and cultural hub in the historical East Slavic lands.
  • A. Smolensk bishopric
    The Smolensk bishopric was a medieval Eastern Orthodox ecclesiastical see centered in the city of Smolensk, playing a key religious and political role in the region’s history.
  • B. Minsk Eparchy
    The Minsk Eparchy is a key diocesan jurisdiction of the Belarusian Orthodox Church, centered in the capital city of Minsk and overseeing local parishes and religious activities in the region.
  • C. Orthodox bishopric of Chełm
    The Orthodox bishopric of Chełm was a historical Eastern Orthodox ecclesiastical jurisdiction centered in the Chełm (Kholm) region, overseeing the spiritual life of local Orthodox Christian communities.
  • D. Smolensk Eparchy
    Smolensk Eparchy is an ecclesiastical jurisdiction of the Russian Orthodox Church centered in the Smolensk region of western Russia.
  • E. Yaroslavl and Rostov Eparchy
    The Yaroslavl and Rostov Eparchy is a diocese of the Russian Orthodox Church centered in the historic cities of Yaroslavl and Rostov, overseeing numerous parishes, monasteries, and cathedrals in the region.
  • F. None of above. chosen

Provenance (2 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_69d8b9f26f18819089c9e43250bee6ae completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4978af9b0819091780281344f5352 completed April 19, 2026, 8:51 a.m.
Created at: April 10, 2026, 10:17 a.m.