Triple

T11042569
Position Surface form Disambiguated ID Type / Status
Subject Sviatoslav Shevchuk E261054 entity
Predicate givenName P17 FINISHED
Object Sviatoslav E431629 NE 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: Sviatoslav | Statement: [Sviatoslav Shevchuk, givenName, Sviatoslav]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sviatoslav
Context triple: [Sviatoslav Shevchuk, givenName, Sviatoslav]
  • A. Sviatoslav chosen
    Sviatoslav is a masculine given name of Slavic origin, historically borne by medieval rulers such as Sviatoslav I of Kiev.
  • B. Oleg
    Oleg is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
  • C. Yaroslav
    Yaroslav is a given name of Slavic origin, commonly used in Eastern Europe and associated with several historical rulers and notable figures.
  • D. Vsevolod
    Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
  • E. Oleg Sviatoslavich
    Oleg Sviatoslavich was a medieval prince of the Rurikid dynasty who ruled over Chernigov and played a significant role in the complex dynastic struggles of Kievan Rus'.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6aa979bdc8190bf0e79104cc098c1 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7980134c8819098122d83380a1f79 completed April 9, 2026, 12:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69e509b8c348819090f118fc69e3441f completed April 19, 2026, 4:58 p.m.
Created at: April 8, 2026, 9:26 p.m.