Triple

T9982751
Position Surface form Disambiguated ID Type / Status
Subject Valentina Tereshkova E196491 entity
Predicate patronymicName P7966 FINISHED
Object Vladimirovna E657616 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: Vladimirovna | Statement: [Valentina Tereshkova, patronymicName, Vladimirovna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vladimirovna
Context triple: [Valentina Tereshkova, patronymicName, Vladimirovna]
  • A. Vladimirovna chosen
    Vladimirovna is a Russian female patronymic indicating that the bearer is the daughter of a man named Vladimir.
  • B. Lyudmila
    Lyudmila is a common Russian female given name, notably borne by figures such as Soviet World War II sniper Lyudmila Pavlichenko.
  • C. Lyudmila
    Lyudmila is a Russian linguist and the former First Lady of Russia, known for being the ex-wife of President Vladimir Putin.
  • D. Danilovna
    Danilovna is a Russian patronymic suffix used for women, indicating "daughter of Danil" or "daughter of Daniel."
  • E. Iosifovna
    Iosifovna is a Russian patronymic suffix used in female names to indicate that the person's father is named Iosif (Joseph).
  • 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_69ca82efbce081908179b4b9c65096eb completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb8bca41081909c04fb77603403b9 completed April 2, 2026, 12:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69d257e888908190a7187e26ba025a44 completed April 5, 2026, 12:39 p.m.
Created at: March 30, 2026, 8:49 p.m.