Triple

T17965154
Position Surface form Disambiguated ID Type / Status
Subject Boris of Kiev E449184 entity
Predicate partOf P40 FINISHED
Object Boris and Gleb 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: Boris and Gleb | Statement: [Boris of Kiev, partOf, Boris and Gleb]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Boris and Gleb
Context triple: [Boris of Kiev, partOf, Boris and Gleb]
  • A. Gleb of Kiev chosen
    Gleb of Kiev was an early 11th-century Kievan Rus' prince venerated as one of the first Russian saints and martyrs, traditionally regarded as a pious son of Vladimir the Great.
  • B. Vsevolod
    Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
  • C. Gavril
    Gavril is a masculine given name, commonly used in Slavic and Eastern European cultures, that derives from the Hebrew name Gabriel.
  • D. Oleg
    Oleg is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
  • E. Vasily
    Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
  • 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_69d8b9f9927c8190a006110c8b996e61 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4b136e4088190ac97fd92dc84a4b9 completed April 19, 2026, 10:40 a.m.
Created at: April 10, 2026, 10:22 a.m.