Triple

T6249216
Position Surface form Disambiguated ID Type / Status
Subject Anatoli Firsov E140003 entity
Predicate givenName P17 FINISHED
Object Anatoli E443521 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: Anatoli | Statement: [Anatoli Firsov, givenName, Anatoli]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Anatoli
Context triple: [Anatoli Firsov, givenName, Anatoli]
  • A. Anatoly chosen
    Anatoly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
  • B. Vyazemsky
    Vyazemsky is a small town in Russia’s Far Eastern Federal District, serving as an administrative center within Khabarovsk Krai.
  • C. Khovrino
    Khovrino is a Moscow Metro station serving as the northern terminus of the Zamoskvoretskaya Line.
  • D. Antoshka
    Antoshka is a common Russian diminutive form of the male given name Anton, often used affectionately or informally.
  • E. Kuntsevskaya
    Kuntsevskaya is a Moscow Metro station on the Big Circle Line serving the Kuntsevo District in western Moscow.
  • 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_69c008b4858c819095b0199114a9a87b completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0633c5f2081909b0246e061f8a7d9 completed March 22, 2026, 9:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69c2441d4ad88190895237d834f5d9b8 completed March 24, 2026, 7:58 a.m.
Created at: March 22, 2026, 4:24 p.m.