Triple
T14353183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viktoria |
E355903
|
entity |
| Predicate | hasSpellingVariant |
P457
|
FINISHED |
| Object | Viktorija |
E355903
|
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: Viktorija | Statement: [Viktoria, hasSpellingVariant, Viktorija]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Viktorija Context triple: [Viktoria, hasSpellingVariant, Viktorija]
-
A.
Viktoria
chosen
Viktoria is a feminine given name of Latin origin, commonly used in various European countries as a variant of "Victoria."
-
B.
Vladimira
Vladimira is a feminine given name, primarily used in Slavic cultures, derived from the male name Vladimir.
-
C.
Elisaveta
Elisaveta is a feminine given name of Slavic origin, commonly used in Eastern Europe as a variant of Elizabeth.
-
D.
Aleksandra
Aleksandra is a feminine given name of Slavic origin, commonly used in various Eastern and Central European countries.
-
E.
Yekaterina
Yekaterina is a common Russian female given name, equivalent to Catherine in English.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8f4ff1e48190bd9419d70098cede |
completed | April 14, 2026, 7:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd550aef908190a7ec49e409f92dc7 |
completed | May 8, 2026, 3:14 a.m. |
Created at: April 10, 2026, 1:14 a.m.