Triple

T10710413
Position Surface form Disambiguated ID Type / Status
Subject Goryacheva E252518 entity
Predicate masculineForm P15475 FINISHED
Object Goryachev E883038 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: Goryachev | Statement: [Goryacheva, masculineForm, Goryachev]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Goryachev
Context triple: [Goryacheva, masculineForm, Goryachev]
  • A. Goryachev chosen
    Goryachev is a Russian surname, typically the masculine form from which the feminine variant "Goryacheva" is derived.
  • B. Alekseyev
    Alekseyev is a Russian surname borne by various notable figures in Russian history, military, and culture.
  • C. Semyonov
    Semyonov is a common Russian surname borne by numerous notable figures in fields such as literature, science, and military history.
  • D. Zubov
    Zubov is a Russian surname most notably associated with figures such as Hockey Hall of Fame defenseman Sergei Zubov.
  • E. Shchusev
    Shchusev is a Russian surname most notably associated with Alexey Shchusev, a prominent Soviet architect known for designing Lenin's Mausoleum in 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_69d6aa5cbabc8190973e683950d89faf completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6fe515b1081909532a20b61ff6cf0 completed April 9, 2026, 1:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69de554ed3848190bba56ab52c05902c completed April 14, 2026, 2:55 p.m.
Created at: April 8, 2026, 9:13 p.m.