Triple

T22045173
Position Surface form Disambiguated ID Type / Status
Subject Mikhail Larionov E544741 entity
Predicate familyName P18 FINISHED
Object Larionov 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: Larionov | Statement: [Mikhail Larionov, familyName, Larionov]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Larionov
Context triple: [Mikhail Larionov, familyName, Larionov]
  • A. Larionov chosen
    Larionov is a person after whom the KLM line is named, likely recognized for notable contributions or significance related to that context.
  • B. Lukyanov
    Lukyanov is a Russian surname borne by various notable figures in politics, science, and the arts.
  • C. Ryazanov
    Ryazanov is a Russian surname most notably borne by Eldar Ryazanov, a celebrated Soviet and Russian film director and screenwriter.
  • D. Korovin
    Korovin is a Russian surname most notably associated with the Impressionist painter Konstantin Korovin.
  • E. Kovalyov
    Kovalyov is the absurdly unfortunate civil servant protagonist of Shostakovich’s opera “The Nose,” whose detached nose gains a higher social rank than he does.
  • 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_69e11e32445c8190ab97089b48a130bb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1282e647481908e054b3ad19e2c15 completed April 28, 2026, 9:35 p.m.
Created at: April 16, 2026, 8:25 p.m.