Triple

T10638701
Position Surface form Disambiguated ID Type / Status
Subject Vasyl E250659 entity
Predicate hasRelatedName P3889 FINISHED
Object Vasilius E101378 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: Vasilius | Statement: [Vasyl, hasRelatedName, Vasilius]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vasilius
Context triple: [Vasyl, hasRelatedName, Vasilius]
  • A. Vsevolod
    Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
  • B. Vasily chosen
    Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
  • C. Dmitry Shemyaka
    Dmitry Shemyaka was a 15th-century Russian prince of the House of Rurik known for his dynastic struggle for the throne of Moscow and his bitter rivalry with Grand Prince Vasili II.
  • D. Vasili the Blind
    Vasili the Blind was a 15th-century Grand Prince of Moscow whose turbulent reign was marked by civil war, dynastic struggle, and the consolidation of Muscovite power.
  • E. Viktor Kulikov
    Viktor Kulikov was a prominent Soviet military leader and Marshal of the Soviet Union who served as Commander-in-Chief of the Warsaw Pact forces during the Cold War.
  • 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_69d6aa5993448190a493b790b8f85010 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6dfaf12188190a5774d4d64674653 completed April 8, 2026, 11:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4cbacad608190adddd91f13e4113b completed April 19, 2026, 12:33 p.m.
Created at: April 8, 2026, 9:04 p.m.