Triple
T13300882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Turgenev |
E316807
|
entity |
| Predicate | patronymicName |
P7966
|
FINISHED |
| Object | Sergeyevich |
E626595
|
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: Sergeyevich | Statement: [Ivan Turgenev, patronymicName, Sergeyevich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sergeyevich Context triple: [Ivan Turgenev, patronymicName, Sergeyevich]
-
A.
Sergeevich
chosen
Sergeevich is a Russian patronymic given name indicating descent from a father named Sergei.
-
B.
Sergei
Sergei is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
-
C.
Grigoryevich
Grigoryevich is a Russian patronymic given name indicating that a person is the son of someone named Grigory.
-
D.
Vasilyevich
Vasilyevich is the Russian patronymic indicating "son of Vasily," famously used in the full name of Ivan IV (Ivan Vasilyevich), the first tsar of Russia.
-
E.
Semyonov
Semyonov is a common Russian surname borne by numerous notable figures in fields such as literature, science, and military history.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d990a43ed88190a8dbbbd7d6d62dc4 |
completed | April 11, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f71f262fd88190ba8871f8761a660b |
completed | May 3, 2026, 10:10 a.m. |
Created at: April 9, 2026, 9:28 p.m.