Triple

T20540801
Position Surface form Disambiguated ID Type / Status
Subject Roman Vladimirovich of Volhynia E504325 entity
Predicate patronymicName P7966 FINISHED
Object Vladimirovich 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: Vladimirovich | Statement: [Roman Vladimirovich of Volhynia, patronymicName, Vladimirovich]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vladimirovich
Context triple: [Roman Vladimirovich of Volhynia, patronymicName, Vladimirovich]
  • A. Vladimirovich chosen
    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.
  • B. Viktorovich
    Viktorovich is a Russian patronymic given name indicating that a person is the son of someone named Viktor.
  • C. Vasilyevich
    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.
  • D. Romanovich
    Romanovich is a Slavic patronymic surname indicating descent from a man named Roman, historically associated with Eastern European nobility such as the rulers of Galicia.
  • E. Yuryevich
    Yuryevich is a Russian patronymic name indicating descent from a father named Yuri (George).
  • 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_69e0b4b476648190bc6019622ae54d3c completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a29224f081908298d104161c5bb9 completed April 20, 2026, 10:02 p.m.
Created at: April 16, 2026, 11:37 a.m.