Triple
T938825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander III of Russia |
E20258
|
entity |
| Predicate | patronymicName |
P7966
|
FINISHED |
| Object | Alexandrovich |
E42868
|
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: Alexandrovich | Statement: [Alexander III of Russia, patronymicName, Alexandrovich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alexandrovich Context triple: [Alexander III of Russia, patronymicName, Alexandrovich]
-
A.
Alexandrovich
chosen
Alexandrovich is the Russian patronymic indicating "son of Alexander," famously used in the full name of Tsar Nicholas II of Russia.
-
B.
Vladimirovich
Vladimirovich is the Russian patronymic derived from the given name Vladimir, indicating "son of Vladimir" and used in full names such as that of Vladimir Putin.
-
C.
Alexey
Alexey is a masculine given name of Slavic origin, commonly used in Russian-speaking countries and derived from the Greek name Alexios, meaning "defender" or "helper."
-
D.
Antonovich
Antonovich is the patronymic of Ivan VI of Russia, indicating he was the son of a man named Anton.
-
E.
Mikhail
Mikhail is a common Russian male given name, famously borne by Soviet leader Mikhail Gorbachev.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b38a3ad4819080d71849e822a12a |
completed | March 1, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a826e0dd188190bf5776a6e4525fdd |
completed | March 4, 2026, 12:34 p.m. |
Created at: March 1, 2026, 7:40 p.m.