Triple

T19457904
Position Surface form Disambiguated ID Type / Status
Subject Leonid Govorov E486781 entity
Predicate familyName P18 FINISHED
Object Govorov 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: Govorov | Statement: [Leonid Govorov, familyName, Govorov]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Govorov
Context triple: [Leonid Govorov, familyName, Govorov]
  • A. Govorov chosen
    Govorov is a Russian surname most notably associated with Leonid Govorov, a prominent Soviet military commander and Marshal of the Soviet Union during World War II.
  • B. Gorokhovets
    Gorokhovets is a historic town in Vladimir Oblast, Russia, known for its well-preserved merchant architecture and scenic location amid the forests and hills of central Russia.
  • C. Kovalyov
    Kovalyov is the absurdly unfortunate civil servant protagonist of Shostakovich’s opera “The Nose,” whose detached nose gains a higher social rank than he does.
  • D. Solovyov
    Solovyov is a Russian surname most notably associated with figures such as philosopher Vladimir Solovyov and various other prominent Russian cultural and public personalities.
  • E. Lukyanov
    Lukyanov is a Russian surname borne by various notable figures in politics, science, and the arts.
  • 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_69d8e8d86d608190bd199a98d0297f27 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e633c569a081908b5a71226345a929 completed April 20, 2026, 2:10 p.m.
Created at: April 10, 2026, 1:38 p.m.