Triple

T8880382
Position Surface form Disambiguated ID Type / Status
Subject Andrei Sverdlov E211395 entity
Predicate familyName P18 FINISHED
Object Sverdlov E217831 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: Sverdlov | Statement: [Andrei Sverdlov, familyName, Sverdlov]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sverdlov
Context triple: [Andrei Sverdlov, familyName, Sverdlov]
  • A. Sverdlov chosen
    Sverdlov is a Russian surname most notably associated with Yakov Sverdlov, a prominent Bolshevik leader during the early Soviet period.
  • B. Kurskaya
    Kurskaya is a Moscow Metro station on the Koltsevaya (Circle) Line, serving as a major transfer hub in the city’s rapid transit network.
  • C. Nikolaev
    Nikolaev is the Russian-language name for Mykolaiv, a major shipbuilding and industrial city in southern Ukraine located near the Black Sea.
  • D. Kuibyshev
    Kuibyshev is the former Soviet name of the Russian city now known as Samara, a major industrial and administrative center on the Volga River.
  • E. Voroshilovsk
    Voroshilovsk was the Soviet-era name of the Russian city now known as Stavropol, reflecting a period when it was renamed in honor of a prominent Soviet military and political figure.
  • 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_69ca838f9e20819096ab1f236a70381a completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc61677c9c8190aa09dc2a05d4cf95 completed April 1, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfabc1992481909e8a4216086d5111 completed April 3, 2026, noon
Created at: March 30, 2026, 6:52 p.m.