Triple
T10030224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wassily |
E204832
|
entity |
| Predicate | transliterationOf |
P5923
|
FINISHED |
| Object | Василий |
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: Василий | Statement: [Wassily, transliterationOf, Василий]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Василий Context triple: [Wassily, transliterationOf, Василий]
-
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.
Василий Александрович
Василий Александрович — князь из династии Рюриковичей, сын Александра Невского и представитель владимиро-суздальской княжеской линии XIII века.
-
D.
Timofei
Timofei is a masculine given name of Slavic origin, commonly used in Russian-speaking countries and related to the name Timo.
-
E.
Vyacheslav
Vyacheslav is a masculine given name of Slavic origin, most notably borne by Soviet politician Vyacheslav Molotov.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcde7ec088190845656cc2529c771 |
completed | April 2, 2026, 2:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d8dbe24a64819098bc94a8a62cc46b |
completed | April 10, 2026, 11:15 a.m. |
Created at: March 30, 2026, 8:54 p.m.