Triple
T1432114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor |
E30470
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Viktor |
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 | Statement: [Victor, hasVariant, Viktor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Viktor Context triple: [Victor, hasVariant, Viktor]
-
A.
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."
-
B.
Eduard
Eduard was the younger son of physicist Albert Einstein, known for his promising studies in psychiatry and his lifelong struggle with schizophrenia.
-
C.
Vasily
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
D.
Ivan
Ivan is a common Slavic male given name widely used in Russia and other Eastern European countries, equivalent to "John" in English.
-
E.
Viktorovich
Viktorovich is a Russian patronymic given name indicating that a person is the son of someone named Viktor.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c4ddbe208190a68cb000a6970d17 |
completed | March 1, 2026, 10:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae719488288190b3f954c037af3d3f |
completed | March 9, 2026, 7:07 a.m. |
Created at: March 1, 2026, 8 p.m.