Triple
T21681140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myortvye dushi |
E535109
|
entity |
| Predicate | notableCharacter |
P1481
|
FINISHED |
| Object | Plyushkin |
—
|
NE NERFINISHED |
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: Plyushkin | Statement: [Myortvye dushi, notableCharacter, Plyushkin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Plyushkin Context triple: [Myortvye dushi, notableCharacter, Plyushkin]
-
A.
Plyushkin
chosen
Plyushkin is a miserly, grotesquely stingy landowner in Nikolai Gogol's novel "Dead Souls," symbolizing the extreme degradation of the human soul through greed and neglect.
-
B.
Nozdryov
Nozdryov is a boisterous, dishonest, and troublemaking landowner in Nikolai Gogol's novel "Dead Souls," known for his compulsive lying and love of gambling and chaos.
-
C.
Vitaly
Vitaly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
D.
Pokryshkin
Pokryshkin is a Russian surname most famously associated with Aleksandr Pokryshkin, a celebrated Soviet World War II fighter ace and marshal of aviation.
-
E.
Vasily
Vasily 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 (2 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96c69990819088a1134ecea09099 |
completed | April 27, 2026, 5:03 p.m. |
Created at: April 16, 2026, 6:43 p.m.