Triple

T4377486
Position Surface form Disambiguated ID Type / Status
Subject Ivan VI Antonovich E99041 entity
Predicate patronymic P7966 FINISHED
Object Antonovich E99041 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: Antonovich | Statement: [Ivan VI Antonovich, patronymic, Antonovich]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Antonovich
Context triple: [Ivan VI Antonovich, patronymic, Antonovich]
  • A. Antonovich chosen
    Antonovich is the patronymic of Ivan VI of Russia, indicating he was the son of a man named Anton.
  • B. Anatolyevich
    Anatolyevich is a Russian patronymic given name indicating that a person is the son of someone named Anatoly.
  • C. Antoshka
    Antoshka is a common Russian diminutive form of the male given name Anton, often used affectionately or informally.
  • D. Pozdnyshev
    Pozdnyshev is the tormented, jealous husband and central narrator of Leo Tolstoy’s novella "The Kreutzer Sonata," whose confession of murdering his wife drives the story’s exploration of marriage, sexuality, and morality.
  • E. Alexandrovich
    Alexandrovich is the Russian patronymic indicating "son of Alexander," famously used in the full name of Tsar Nicholas II of Russia.
  • 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_69b3454ea8f48190a49c2436624d6ef6 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3523ed220819090cef1a7933489d9 completed March 12, 2026, 11:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5e51907688190ad964d341eb84529 completed March 14, 2026, 10:45 p.m.
Created at: March 12, 2026, 11:18 p.m.