Triple
T3234310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viacheslav Fetisov |
E67814
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Viacheslav |
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: Viacheslav | Statement: [Viacheslav Fetisov, givenName, Viacheslav]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Viacheslav Context triple: [Viacheslav Fetisov, givenName, Viacheslav]
-
A.
Vyacheslav
chosen
Vyacheslav is a masculine given name of Slavic origin, most notably borne by Soviet politician Vyacheslav Molotov.
-
B.
Vsevolod
Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
-
C.
Vladimir
Vladimir is a common Russian male given name of Slavic origin, historically associated with rulers and notably borne by Russian president Vladimir Putin.
-
D.
Vladimir
Vladimir is a historic Russian city east of Moscow, known as one of the medieval capitals of Russia and a key center of the Golden Ring.
-
E.
Vasily
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
- 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_69ad858d27348190abb61c280b4c86a9 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaedcd9588190b3623f0109d653a4 |
completed | March 8, 2026, 5:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5560426908190bd9620900e370634 |
completed | March 14, 2026, 12:35 p.m. |
Created at: March 8, 2026, 3:08 p.m.