Triple

T17736294
Position Surface form Disambiguated ID Type / Status
Subject Alexis Mikhailovich E442726 entity
Predicate patronymicName P7966 FINISHED
Object Mikhailovich 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: Mikhailovich | Statement: [Alexis Mikhailovich, patronymicName, Mikhailovich]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mikhailovich
Context triple: [Alexis Mikhailovich, patronymicName, Mikhailovich]
  • A. Mikhailovich chosen
    Mikhailovich is a Russian patronymic indicating "son of Mikhail," commonly used as the middle name in Russian naming conventions.
  • B. Mikhail
    Mikhail is a common Russian male given name, famously borne by Soviet leader Mikhail Gorbachev.
  • C. Milyutin
    Milyutin is a Russian surname most notably associated with Dmitry Milyutin, the 19th-century Imperial Russian war minister and military reformer.
  • D. Matakevich
    Matakevich is a surname most notably borne by American football linebacker and special teams standout Tyler Matakevich.
  • E. Rodion Malinovsky
    Rodion Malinovsky was a prominent Soviet military commander and Marshal of the Soviet Union who played a key role in major Eastern Front operations during World War II and later served as the USSR’s Minister of Defense.
  • 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e478ec48988190a503f9aafeab6d23 completed April 19, 2026, 6:40 a.m.
Created at: April 10, 2026, 10:08 a.m.