Triple
T3549738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daniil Aleksandrovich of Moscow |
E75081
|
entity |
| Predicate | patronymic |
P7966
|
FINISHED |
| Object | Aleksandrovich |
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: Aleksandrovich | Statement: [Daniil Aleksandrovich of Moscow, patronymic, Aleksandrovich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aleksandrovich Context triple: [Daniil Aleksandrovich of Moscow, patronymic, Aleksandrovich]
-
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.
Alekseevich
Alekseevich is a Russian patronymic surname or middle name derived from the given name Aleksey, indicating "son of Aleksey."
-
C.
Aleksandr
Aleksandr is a common Russian male given name of Greek origin, equivalent to Alexander in English.
-
D.
Viktorovich
Viktorovich is a Russian patronymic given name indicating that a person is the son of someone named Viktor.
-
E.
Nikolaevich
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.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfd38c8c8190a4591689ad57c998 |
completed | March 8, 2026, 6:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b38be9335c81909ba546a079134c8f |
completed | March 13, 2026, 4 a.m. |
Created at: March 8, 2026, 3:20 p.m.