Triple

T18523443
Position Surface form Disambiguated ID Type / Status
Subject Rodion Malinovsky E452650 entity
Predicate givenName P17 FINISHED
Object Rodion 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: Rodion | Statement: [Rodion Malinovsky, givenName, Rodion]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rodion
Context triple: [Rodion Malinovsky, givenName, Rodion]
  • A. Rodion chosen
    Rodion is a masculine given name of Slavic origin, most notably borne by Soviet military commander Rodion Malinovsky.
  • B. Alyosha Skvortsov
    Alyosha Skvortsov is the young, idealistic Soviet soldier who serves as the central protagonist in the classic 1959 war film "Ballad of a Soldier."
  • C. Vasily
    Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
  • D. Viktor Chebrikov
    Viktor Chebrikov was a Soviet politician and security official who served as Chairman of the KGB during the 1980s, playing a key role in the late Cold War intelligence apparatus.
  • E. Konstantin Vershinin
    Konstantin Vershinin was a prominent Soviet military leader who served as a senior commander of the Soviet Air Forces during and after World War II.
  • 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_69d8d387b5548190aa030dad2cb4947e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5338f6da48190bdb374019d10db05 completed April 19, 2026, 7:57 p.m.
Created at: April 10, 2026, 11:37 a.m.