Triple
T9639693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vsevolod Pudovkin |
E233030
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Vsevolod |
E254630
|
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: Vsevolod | Statement: [Vsevolod Pudovkin, givenName, Vsevolod]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vsevolod Context triple: [Vsevolod Pudovkin, givenName, Vsevolod]
-
A.
Vsevolod
chosen
Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
-
B.
Vasily
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
C.
Oleg
Oleg is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
-
D.
Vsevolodovich
Vsevolodovich is the patronymic indicating that Vladimir II Monomakh was the son of Vsevolod, a ruler of Kievan Rus'.
-
E.
Sviatoslav
Sviatoslav is a masculine given name of Slavic origin, historically borne by medieval rulers such as Sviatoslav I of Kiev.
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b532aa4819087b56be6f5635126 |
completed | April 1, 2026, 10:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d316faaed48190aa51e52b5b774cd8 |
completed | April 6, 2026, 2:14 a.m. |
Created at: March 30, 2026, 8:12 p.m.