Triple

T7681812
Position Surface form Disambiguated ID Type / Status
Subject Wiktor E174012 entity
Predicate hasVariant P455 FINISHED
Object Wiktor (Polish form of Victor) E174012 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: Wiktor (Polish form of Victor) | Statement: [Wiktor, hasVariant, Wiktor (Polish form of Victor)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wiktor (Polish form of Victor)
Context triple: [Wiktor, hasVariant, Wiktor (Polish form of Victor)]
  • A. Wiktor chosen
    Wiktor is a masculine given name, primarily used in Slavic countries, that corresponds to the name Victor.
  • B. Viktorovich
    Viktorovich is a Russian patronymic given name indicating that a person is the son of someone named Viktor.
  • C. Wojciech
    Wojciech is a masculine given name of Slavic origin, particularly common in Poland.
  • D. Piotr
    Piotr is the Polish form of the given name Peter, commonly used in Poland and among Polish-speaking communities.
  • E. Viktor
    Viktor is the given name of Viktor Frankl, the Austrian neurologist, psychiatrist, and Holocaust survivor who founded logotherapy and wrote "Man’s Search for Meaning."
  • 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_69c6995840408190a19de6c51090f46f completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c70201387c8190afc8479b5a9e21e8 completed March 27, 2026, 10:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8a25304b88190920c2e4908925ce2 completed March 29, 2026, 3:53 a.m.
Created at: March 27, 2026, 4:01 p.m.