Triple

T20654869
Position Surface form Disambiguated ID Type / Status
Subject Vsevolodovich E507596 entity
Predicate derivedFromGivenName P17 FINISHED
Object Vsevolod 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: Vsevolod | Statement: [Vsevolodovich, derivedFromGivenName, Vsevolod]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vsevolod
Context triple: [Vsevolodovich, derivedFromGivenName, Vsevolod]
  • A. Vsevolod chosen
    Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
  • B. Vsevolod Vladimirovich
    Vsevolod Vladimirovich was a medieval Rus' prince of the Rurikid dynasty, known as a son of Rogneda of Polotsk and a member of the ruling elite of Kievan Rus'.
  • C. Vsevolod Yuryevich
    Vsevolod Yuryevich was a 12th-century prince of the Rurikid dynasty, notable as a son of Yuri Dolgorukiy and a regional ruler in the fragmented Kievan Rus'.
  • D. Vasily
    Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
  • E. Yuri Vsevolodovich
    Yuri Vsevolodovich was a Grand Prince of Vladimir in the early 13th century, known for his role in consolidating the Vladimir-Suzdal principality and for being killed during the Mongol invasion of Rus'.
  • 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_69e0b4bf58c081908e52a4500e03ff83 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6b2ec90e881909250884483429acf completed April 20, 2026, 11:12 p.m.
Created at: April 16, 2026, 11:43 a.m.