Triple

T22174821
Position Surface form Disambiguated ID Type / Status
Subject Štěpán E548019 entity
Predicate hasVariant P455 FINISHED
Object Stepan (without diacritics) 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: Stepan (without diacritics) | Statement: [Štěpán, hasVariant, Stepan (without diacritics)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stepan (without diacritics)
Context triple: [Štěpán, hasVariant, Stepan (without diacritics)]
  • A. Stepanovich
    Stepanovich is a Russian patronymic derived from the male given name Stepan, traditionally indicating "son of Stepan."
  • B. Stepanov
    Stepanov is a Slavic surname commonly derived from the given name Stepan, borne by various notable figures in fields such as mathematics, sports, and the arts.
  • C. Stepan chosen
    Stepan is the given name of Stephen Timoshenko, a pioneering engineer widely regarded as the father of modern engineering mechanics.
  • D. Stepanovna
    Stepanovna is the Russian patronymic derived from the male given name Stepan, indicating "daughter of Stepan."
  • E. Štěpán
    Štěpán is the Czech given name corresponding to the Hungarian name István, itself equivalent to Stephen in English.
  • 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_69e11e3d53f88190a2b690e3f25bb062 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12a6b755c81909e9bd2a588c065b3 completed April 28, 2026, 9:45 p.m.
Created at: April 16, 2026, 8:34 p.m.