Triple

T21691339
Position Surface form Disambiguated ID Type / Status
Subject Sedov E535375 entity
Predicate hasTransliteration P2508 FINISHED
Object Седов 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: Седов | Statement: [Sedov, hasTransliteration, Седов]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Седов
Context triple: [Sedov, hasTransliteration, Седов]
  • A. Sampsonievsky
    Sampsonievsky is a municipal settlement located within the Vyborgsky District of Saint Petersburg, Russia.
  • B. Sedov chosen
    Sedov is a Russian surname most notably associated with Lev Sedov, the revolutionary son of Leon Trotsky.
  • C. Golovin
    Golovin is a Russian surname historically borne by various notable figures in politics, the military, and the arts.
  • D. Semyen
    Semyen is a masculine given name, commonly used in Slavic countries as a variant of the name Semyon.
  • E. Sergiyev
    Sergiyev is the former name of the Russian town now known as Sergiyev Posad, a historic center of Orthodox Christianity northeast of Moscow.
  • 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_69e0c46a6ee481908836e1420fb78c9b completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef96cfaab08190b400e1538afc8c43 completed April 27, 2026, 5:03 p.m.
Created at: April 16, 2026, 6:45 p.m.