Triple
T5063825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vyacheslav Kozlov |
E114093
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Vyacheslav |
E203208
|
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: Vyacheslav | Statement: [Vyacheslav Kozlov, givenName, Vyacheslav]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vyacheslav Context triple: [Vyacheslav Kozlov, givenName, Vyacheslav]
-
A.
Vyacheslav
chosen
Vyacheslav is a masculine given name of Slavic origin, most notably borne by Soviet politician Vyacheslav Molotov.
-
B.
Nikolai Vatutin
Nikolai Vatutin was a prominent Soviet general of World War II who played a key role in major Eastern Front offensives, including the defense and counteroffensives around Kursk.
-
C.
Vsevolod
Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
-
D.
Rodion Yakovlev
Rodion Yakovlev was a high-ranking Soviet military leader who attained the prestigious title of Marshal of the Soviet Union.
-
E.
Kuzma Derevyanko
Kuzma Derevyanko was a Soviet general who served as the USSR’s representative at the Japanese surrender ceremony ending World War II.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd747756bc8190863c426e6fd6e8f7 |
completed | March 20, 2026, 4:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bfd7104f008190b2bcacc8d071277c |
completed | March 22, 2026, 11:48 a.m. |
Created at: March 20, 2026, 1:38 p.m.