Triple
T8624388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasili Shukshin |
E204247
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Vasili |
E101378
|
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: Vasili | Statement: [Vasili Shukshin, givenName, Vasili]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vasili Context triple: [Vasili Shukshin, givenName, Vasili]
-
A.
Vasily
chosen
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
B.
Vsevolod
Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
-
C.
Vyacheslav
Vyacheslav is a masculine given name of Slavic origin, most notably borne by Soviet politician Vyacheslav Molotov.
-
D.
Grigory Spiridov
Grigory Spiridov was a prominent 18th-century Russian admiral best known for his leadership in the Russo-Turkish War, particularly at the Battle of Chesma.
-
E.
Voloshin
Voloshin is a Russian surname most notably associated with the poet and literary critic Maximilian Voloshin, a key figure of the Silver Age of Russian poetry.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4728360c8190b5e600596cbced0c |
completed | March 31, 2026, 10:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfa00aa93c819094884d5bbaa5a264 |
completed | April 3, 2026, 11:10 a.m. |
Created at: March 30, 2026, 6:26 p.m.