Triple
T1139167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Duke Michael Alexandrovich of Russia |
E23409
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Mikhail |
E36451
|
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: Mikhail | Statement: [Grand Duke Michael Alexandrovich of Russia, givenName, Mikhail]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mikhail Context triple: [Grand Duke Michael Alexandrovich of Russia, givenName, Mikhail]
-
A.
Mikhail
chosen
Mikhail is a common Russian male given name, famously borne by Soviet leader Mikhail Gorbachev.
-
B.
Nikolay
Nikolay is a masculine given name of Slavic origin, commonly used in Russian-speaking countries and equivalent to Nicholas in English.
-
C.
Pyotr
Pyotr is the Russian given name of Peter Kropotkin, the influential 19th-century anarchist philosopher, geographer, and revolutionary.
-
D.
Sergei
Sergei is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
-
E.
Leonid
Leonid is a masculine given name of Slavic origin, notably borne by Soviet leader Leonid Brezhnev.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc27c88881909c64ec30b7f66575 |
completed | March 1, 2026, 10:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adf3a85f8481908d93f60b0ae82901 |
completed | March 8, 2026, 10:09 p.m. |
Created at: March 1, 2026, 7:44 p.m.