Triple

T5116452
Position Surface form Disambiguated ID Type / Status
Subject Prince Pyotr Vasilyevich Urusov E115346 entity
Predicate patronymicName P7966 FINISHED
Object Vasilyevich E375781 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: Vasilyevich | Statement: [Prince Pyotr Vasilyevich Urusov, patronymicName, Vasilyevich]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vasilyevich
Context triple: [Prince Pyotr Vasilyevich Urusov, patronymicName, Vasilyevich]
  • A. Vasilyevich chosen
    Vasilyevich is the Russian patronymic indicating "son of Vasily," famously used in the full name of Ivan IV (Ivan Vasilyevich), the first tsar of Russia.
  • B. Viktorovich
    Viktorovich is a Russian patronymic given name indicating that a person is the son of someone named Viktor.
  • C. Vladimirovich
    Vladimirovich is the Russian patronymic derived from the given name Vladimir, indicating "son of Vladimir" and used in full names such as that of Vladimir Putin.
  • D. Vasily
    Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
  • E. Vasily Vasiliev
    Vasily Vasiliev is a descendant of Soviet leader Joseph Stalin’s family line, being the son of Stalin’s son Vasily Stalin.
  • 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_69bd4441d1648190a54a533895041987 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd75cfa9f88190aa7dfd264e554899 completed March 20, 2026, 4:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69bebaafd674819080b751216e5b6f70 completed March 21, 2026, 3:35 p.m.
Created at: March 20, 2026, 1:41 p.m.