Triple
T9165928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yefimovich |
E219955
|
entity |
| Predicate | patronymicFrom |
P7966
|
FINISHED |
| Object | Yefim |
E219955
|
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: Yefim | Statement: [Yefimovich, patronymicFrom, Yefim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yefim Context triple: [Yefimovich, patronymicFrom, Yefim]
-
A.
Yefimovich
chosen
Yefimovich is the Russian patronymic derived from the male given name Yefim, famously borne by Grigori Rasputin as part of his full name.
-
B.
Semyon
Semyon is a masculine given name of Russian origin, commonly used in Slavic countries.
-
C.
Yefremov
Yefremov is a town in western Russia known as a local administrative and economic center within Tula Oblast.
-
D.
Yakov
Yakov was the eldest son of Soviet leader Joseph Stalin, known for his troubled relationship with his father and his death as a prisoner of war during World War II.
-
E.
Yevgeny
Yevgeny 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_69ca83e3633c81908688a9fa2306ba99 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaa3055048190870211449c78fc4e |
completed | April 1, 2026, 5:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d065cd42f481909ad3c68372041b1a |
completed | April 4, 2026, 1:13 a.m. |
Created at: March 30, 2026, 7:22 p.m.