Triple

T11501007
Position Surface form Disambiguated ID Type / Status
Subject Ber Borochov E272662 entity
Predicate familyName P18 FINISHED
Object Borochov E272662 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: Borochov | Statement: [Ber Borochov, familyName, Borochov]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Borochov
Context triple: [Ber Borochov, familyName, Borochov]
  • A. Ussishkin
    Ussishkin is a Jewish family name most prominently associated with Zionist leader Menachem Ussishkin.
  • B. Yakov Slashchov
    Yakov Slashchov was a Russian Imperial and later White Army general best known for leading anti-Bolshevik forces in southern Russia and Crimea during the Russian Civil War.
  • C. Yagoda
    Yagoda is a Russian surname most notably associated with Genrikh Yagoda, a Soviet secret police official and early head of the NKVD under Joseph Stalin.
  • D. Ber Borochov chosen
    Ber Borochov was a Marxist Zionist theorist and one of the founding ideologues of socialist Zionism, whose ideas strongly influenced the Poale Zion movement.
  • E. Joffe
    Joffe is a surname most notably associated with Adolf Joffe, a prominent early 20th-century Russian revolutionary and diplomat.
  • 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_69d6aae1b09881909ce2ded3fa0c14fa completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d85de3e9c881909d6c55334f7a832d completed April 10, 2026, 2:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69e604bc1d3c81908497f1d19dcc2167 completed April 20, 2026, 10:49 a.m.
Created at: April 8, 2026, 9:36 p.m.