Triple

T17333016
Position Surface form Disambiguated ID Type / Status
Subject New Hieromartyr Vladimir (Bogoyavlensky) E420861 entity
Predicate name P16 FINISHED
Object Vladimir (Bogoyavlensky) NE NERFINISHED

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: Vladimir (Bogoyavlensky) | Statement: [New Hieromartyr Vladimir (Bogoyavlensky), name, Vladimir (Bogoyavlensky)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vladimir (Bogoyavlensky)
Context triple: [New Hieromartyr Vladimir (Bogoyavlensky), name, Vladimir (Bogoyavlensky)]
  • A. Vsevolod
    Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
  • B. Vladimir
    Vladimir is a historic Russian city east of Moscow, known as one of the medieval capitals of Russia and a key center of the Golden Ring.
  • C. Vladimir chosen
    Vladimir is a common Russian male given name of Slavic origin, historically associated with rulers and notably borne by Russian president Vladimir Putin.
  • D. Vasily
    Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
  • E. Vladimirko Volodarovich
    Vladimirko Volodarovich was a medieval Rus' prince who ruled the principality of Volhynia in what is now western Ukraine.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d889d3adc881909319f1edb8d2a956 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43a0fa57881909071fd395b3d46c4 completed April 19, 2026, 2:12 a.m.
Created at: April 10, 2026, 5:43 a.m.