Triple
T3874056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleksey Mikhailovich Romanov |
E92454
|
entity |
| Predicate | patronymicName |
P7966
|
FINISHED |
| Object | Mikhailovich |
E362226
|
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: Mikhailovich | Statement: [Aleksey Mikhailovich Romanov, patronymicName, Mikhailovich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mikhailovich Context triple: [Aleksey Mikhailovich Romanov, patronymicName, Mikhailovich]
-
A.
Mikhail
Mikhail is a common Russian male given name, famously borne by Soviet leader Mikhail Gorbachev.
-
B.
Rodion Malinovsky
Rodion Malinovsky was a prominent Soviet military commander and Marshal of the Soviet Union who played a key role in major Eastern Front operations during World War II and later served as the USSR’s Minister of Defense.
-
C.
Vyacheslav
Vyacheslav is a masculine given name of Slavic origin, most notably borne by Soviet politician Vyacheslav Molotov.
-
D.
Semyon
Semyon is a masculine given name of Russian origin, commonly used in Slavic countries.
-
E.
Mikhaylovich
chosen
Mikhaylovich is a Russian patronymic name indicating that a person is the son of someone named Mikhail.
- 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec59bea08190b1e193f34944a2ee |
completed | March 9, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bee05440cc8190b0ab8d0c0811899b |
completed | March 21, 2026, 6:15 p.m. |
Created at: March 9, 2026, 3:20 p.m.