Triple

T18957366
Position Surface form Disambiguated ID Type / Status
Subject Nina Ivanovna Yakushova E463815 entity
Predicate patronymicName P7966 FINISHED
Object Ivanovna 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: Ivanovna | Statement: [Nina Ivanovna Yakushova, patronymicName, Ivanovna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ivanovna
Context triple: [Nina Ivanovna Yakushova, patronymicName, Ivanovna]
  • A. Ivanovna chosen
    Ivanovna is a common Russian patronymic surname suffix for women, indicating "daughter of Ivan."
  • B. Vasilyevna
    Vasilyevna is a Russian female patronymic name indicating that the person's father is named Vasily.
  • C. Iosifovna
    Iosifovna is a Russian patronymic suffix used in female names to indicate that the person's father is named Iosif (Joseph).
  • D. Stepanida Ivanovna
    Stepanida Ivanovna is known primarily as the mother of Irina Godunova, the wife of Tsar Feodor I of Russia and sister of Tsar Boris Godunov.
  • E. Mikhailovna
    Mikhailovna is a Russian patronymic indicating descent from a father named Mikhail, commonly used as the middle name in female full names.
  • 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_69d8dcffc278819086792a4ebfddfafa completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d5cee8348190b6506b10aed6c58a completed April 20, 2026, 7:29 a.m.
Created at: April 10, 2026, noon