Triple
T287842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander |
E5923
|
entity |
| Predicate | variant |
P4680
|
FINISHED |
| Object | Aleksandr |
E56933
|
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: Aleksandr | Statement: [Alexander, variant, Aleksandr]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aleksandr Context triple: [Alexander, variant, Aleksandr]
-
A.
Mikhail
Mikhail is a common Russian male given name, famously borne by Soviet leader Mikhail Gorbachev.
-
B.
Aleksander
chosen
Aleksander is a given name, commonly used in Slavic and Scandinavian countries, that corresponds to the name Alexander.
-
C.
Alexandrovich
Alexandrovich is the Russian patronymic indicating "son of Alexander," famously used in the full name of Tsar Nicholas II of Russia.
-
D.
Alexei Petrovich, Tsarevich of Russia
Alexei Petrovich, Tsarevich of Russia, was the ill-fated heir to the Russian throne whose conflict with his father Peter the Great led to his arrest, torture, and death in custody.
-
E.
Vladimir
Vladimir is a common Russian male given name of Slavic origin, historically associated with rulers and notably borne by Russian president Vladimir Putin.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e2ddaa88190b08c40b5823f30a0 |
completed | Feb. 28, 2026, 3:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a457fa35988190851216c84ad63232 |
completed | March 1, 2026, 3:15 p.m. |
Created at: Feb. 28, 2026, 3:02 a.m.