Triple
T906215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicholas I of Russia |
E19554
|
entity |
| Predicate | patronymicName |
P7966
|
FINISHED |
| Object | Pavlovich |
E107074
|
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: Pavlovich | Statement: [Nicholas I of Russia, patronymicName, Pavlovich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pavlovich Context triple: [Nicholas I of Russia, patronymicName, Pavlovich]
-
A.
Pavlovich
chosen
Pavlovich is the Russian patronymic indicating "son of Pavel," used in the full name of Emperor Alexander I of Russia.
-
B.
Petrovich
Petrovich is a Russian patronymic meaning "son of Pyotr (Peter)," commonly used as a middle name in Russian naming conventions.
-
C.
Vasilevsky
Vasilevsky is a Russian surname most prominently associated with Aleksandr Vasilevsky, a leading Soviet military commander and Marshal of the Soviet Union during World War II.
-
D.
Pavel
Pavel is a Slavic given name, equivalent to the English name Paul.
-
E.
Vasily
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b2cc85a08190bc8186eb9ed1fa38 |
completed | March 1, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac5e990be881908b47d88074339470 |
completed | March 7, 2026, 5:21 p.m. |
Created at: March 1, 2026, 7:39 p.m.