Triple

T22220841
Position Surface form Disambiguated ID Type / Status
Subject Soviet 54th Army E549203 entity
Predicate notableCommander P1197 FINISHED
Object Grigory Kulik 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: Grigory Kulik | Statement: [Soviet 54th Army, notableCommander, Grigory Kulik]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Grigory Kulik
Context triple: [Soviet 54th Army, notableCommander, Grigory Kulik]
  • A. Grigory Kulik chosen
    Grigory Kulik was a Soviet military commander and marshal known for his influential yet often controversial role in the Red Army’s leadership before and during World War II.
  • B. Yevgeny Kulik
    Yevgeny Kulik is a notable individual who carries the Russian surname Kulik, associated with various prominent figures in Russian cultural and public life.
  • C. Pavel Kulik
    Pavel Kulik is a person notable enough to be recognized as a bearer of the surname Kulik.
  • D. Oleg Kulik
    Oleg Kulik is a Russian performance artist best known for his provocative “man-dog” performances that explore themes of dehumanization, power, and social control.
  • E. Dmitry Kulik
    Dmitry Kulik is a notable individual who shares the surname Kulik, recognized as a distinguished bearer of that name.
  • 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_69e11e403d6481909a94d0aaf157f6ef completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12b90b1dc81908fee5fab8d5d14a2 completed April 28, 2026, 9:50 p.m.
Created at: April 16, 2026, 8:37 p.m.