Triple

T10422927
Position Surface form Disambiguated ID Type / Status
Subject Oleh E245704 entity
Predicate hasTransliteration P2508 FINISHED
Object Олег E357811 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: Олег | Statement: [Oleh, hasTransliteration, Олег]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Олег
Context triple: [Oleh, hasTransliteration, Олег]
  • A. Oleg chosen
    Oleg is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
  • B. 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'.
  • C. Vsevolod
    Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
  • D. Sviatoslav
    Sviatoslav is a masculine given name of Slavic origin, historically borne by medieval rulers such as Sviatoslav I of Kiev.
  • E. Sviatoslav Olgovich
    Sviatoslav Olgovich was a 12th-century prince from the Olgovichi branch of the Rurikid dynasty who ruled in parts of Kievan Rus' and took part in its dynastic conflicts.
  • 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_69d381bf3dc08190bf35a2643e4e8f22 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4ea2de4d48190aee65b3f6ec3cc48 completed April 7, 2026, 11:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69d95e5197cc8190ad70c665ec2f8fa8 completed April 10, 2026, 8:32 p.m.
Created at: April 6, 2026, 12:12 p.m.