Triple

T9164477
Position Surface form Disambiguated ID Type / Status
Subject Mikhail Sverdlov E219914 entity
Predicate father P120 FINISHED
Object Yakov Sverdlov E38200 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: Yakov Sverdlov | Statement: [Mikhail Sverdlov, father, Yakov Sverdlov]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yakov Sverdlov
Context triple: [Mikhail Sverdlov, father, Yakov Sverdlov]
  • A. Yakov Sverdlov chosen
    Yakov Sverdlov was a prominent Bolshevik revolutionary and early Soviet statesman who served as the first head of state of Soviet Russia following the October Revolution.
  • B. Mikhail Sverdlov
    Mikhail Sverdlov was the son of prominent Bolshevik leader Yakov Sverdlov, associated with the early Soviet political elite.
  • C. Andrei Sverdlov
    Andrei Sverdlov was the son of prominent Bolshevik leader Yakov Sverdlov and a Soviet figure whose life was closely tied to the legacy of his revolutionary family.
  • D. Vladimir Sverdlov
    Vladimir Sverdlov is a Russian individual notable enough to be recognized as a prominent bearer of the Sverdlov surname.
  • E. Grigory Zinoviev
    Grigory Zinoviev was a prominent early Bolshevik leader, close associate of Lenin, and later a key victim of Stalin’s Great Purge, executed after a major show trial.
  • 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_69ca83e3633c81908688a9fa2306ba99 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccaa2ee64c8190a9a5abafe5d0b086 completed April 1, 2026, 5:16 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0c6fd5d4481909300c5101304f35f completed April 4, 2026, 8:08 a.m.
Created at: March 30, 2026, 7:21 p.m.