Triple
T1505225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikhail Tukhachevsky |
E33884
|
entity |
| Predicate | patronymicName |
P7966
|
FINISHED |
| Object | Nikolayevich |
E159249
|
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: Nikolayevich | Statement: [Mikhail Tukhachevsky, patronymicName, Nikolayevich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nikolayevich Context triple: [Mikhail Tukhachevsky, patronymicName, Nikolayevich]
-
A.
Nikolaevich
chosen
Nikolaevich is a Russian patronymic meaning "son of Nikolai," commonly used in the full names of male members of the Russian imperial family and others bearing the given name Nikolai.
-
B.
Nikolay
Nikolay is a masculine given name of Slavic origin, commonly used in Russian-speaking countries and equivalent to Nicholas in English.
-
C.
Fyodorovich
Fyodorovich is the patronymic indicating descent from a father named Fyodor, notably used in the full name of Mikhail I of Russia.
-
D.
Viktorovich
Viktorovich is a Russian patronymic given name indicating that a person is the son of someone named Viktor.
-
E.
Alexandrovich
Alexandrovich is the Russian patronymic indicating "son of Alexander," famously used in the full name of Tsar Nicholas II of Russia.
- 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a88734508481909378bb3e86e13323 |
completed | March 4, 2026, 7:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae6adcef5881908cefd7d575b85323 |
completed | March 9, 2026, 6:38 a.m. |
Created at: March 4, 2026, 7:24 p.m.