Triple
T8877102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Víctor |
E211313
|
entity |
| Predicate | cognateOf |
P8954
|
FINISHED |
| Object | Viktor (Slavic given name) |
E75938
|
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: Viktor (Slavic given name) | Statement: [Víctor, cognateOf, Viktor (Slavic given name)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Viktor (Slavic given name) Context triple: [Víctor, cognateOf, Viktor (Slavic given name)]
-
A.
Viktorovich
Viktorovich is a Russian patronymic given name indicating that a person is the son of someone named Viktor.
-
B.
Vladimirovich
Vladimirovich is the Russian patronymic derived from the given name Vladimir, indicating "son of Vladimir" and used in full names such as that of Vladimir Putin.
-
C.
Viktor
chosen
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."
-
D.
Viktor
Viktor is a powerful and ancient vampire elder from the "Underworld" film series, portrayed by actor Bill Nighy.
-
E.
Yuriĭ
Yuriĭ is a given name of Slavic origin, commonly used as a variant of the name Yuri.
- 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61472cc081909e51b4a35a20ef43 |
completed | April 1, 2026, 12:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfabaf57b88190a71d5303767ab517 |
completed | April 3, 2026, 11:59 a.m. |
Created at: March 30, 2026, 6:52 p.m.