Triple
T9097544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuri Lyubimov |
E218065
|
entity |
| Predicate | patronymicName |
P7966
|
FINISHED |
| Object | Petrovich |
E105551
|
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: Petrovich | Statement: [Yuri Lyubimov, patronymicName, Petrovich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Petrovich Context triple: [Yuri Lyubimov, patronymicName, Petrovich]
-
A.
Petrovich
chosen
Petrovich is a Russian patronymic meaning "son of Pyotr (Peter)," commonly used as a middle name in Russian naming conventions.
-
B.
Pavlovich
Pavlovich is the Russian patronymic indicating "son of Pavel," used in the full name of Emperor Alexander I of Russia.
-
C.
Peshkov
Peshkov is a Russian surname most famously borne by Alexei Maximovich Peshkov, better known by his pen name Maxim Gorky, a prominent writer and political activist.
-
D.
Peter Petrovich
Peter Petrovich was a Russian imperial prince, the son of Empress Catherine I of Russia and a member of the early 18th-century Romanov dynasty.
-
E.
Christianovich
Christianovich was an architect or engineer known for designing the historic Bank Bridge in Saint Petersburg, Russia.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc96b7d0d48190a3b15f35bef087e3 |
completed | April 1, 2026, 3:53 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0181a9ae88190ab80d4e80e919f42 |
completed | April 3, 2026, 7:42 p.m. |
Created at: March 30, 2026, 7:15 p.m.