Triple

T30881599
Position Surface form Disambiguated ID Type / Status
Subject Yefimovna E786628 entity
Predicate correspondingMasculinePatronymic P178074 FINISHED
Object Yefimovich LITERAL 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: Yefimovich | Statement: [Yefimovna, correspondingMasculinePatronymic, Yefimovich]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: correspondingMasculinePatronymic
Context triple: [Yefimovna, correspondingMasculinePatronymic, Yefimovich]
  • A. patronymicName
    Indicates that one entity’s name is derived from or based on the given name of a parent or ancestor, typically the father.
  • B. patronymicOrMatronymic
    Indicates that one entity’s name is derived from the father’s or mother’s name, expressing a parent-based naming relationship between the two entities.
  • C. isPatronymicName
    Indicates that a name is derived from a father’s or ancestor’s given name, typically signifying lineage or descent.
  • D. patriarchalName
    Indicates that one entity bears a name derived from or assigned according to a patriarchal (male-line or father-based) naming convention in relation to another entity.
  • E. patronymicOrigin
    Indicates that one entity’s name is derived from the name of a father or paternal ancestor of another entity.
  • F. None of above. chosen

Provenance (4 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_69f224bae17c8190bb3a6a28e3d019df completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f707f7959881908f037f0d6b1d0c36 completed May 3, 2026, 8:31 a.m.
PD Predicate disambiguation batch_69f700fc274c8190a128593dc7c7abd0 completed May 3, 2026, 8:02 a.m.
PDg Predicate description generation batch_69f707f380388190954b79d52a321921 completed May 3, 2026, 8:31 a.m.
Created at: April 29, 2026, 8:48 p.m.