Triple

T1974104
Position Surface form Disambiguated ID Type / Status
Subject Alexandrovich E42868 entity
Predicate instanceOf P0 FINISHED
Object Russian-language patronymic C8491 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: Russian-language patronymic
Context triple: [Alexandrovich, instanceOf, Russian-language patronymic]
  • A. Russian patronymic
    A Russian patronymic is a middle name derived from a person's father's given name, typically formed with gendered suffixes to indicate "son of" or "daughter of" in Russian naming conventions.
  • B. Russian patronymic chosen
    A Russian patronymic is a middle name derived from a person's father's given name, modified with gender-specific suffixes to indicate "son of" or "daughter of" in Russian naming conventions.
  • C. patronymic
    A patronymic is a name derived from the given name of a father or male ancestor, typically used to indicate lineage or descent.
  • D. patronymic
    A patronymic is a component of a personal name derived from the given name of a father or paternal ancestor, often indicating lineage or descent.
  • E. Korean given name
    A Korean given name is a personal name, typically consisting of two syllables written in Hangul (and sometimes Hanja), chosen to convey specific meanings, virtues, or aspirations for the individual.
  • F. None of above.

Provenance (1 batch)

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_69a8871289048190b00b0d7744b7b2b1 completed March 4, 2026, 7:25 p.m.
Created at: March 4, 2026, 7:36 p.m.