Triple
T9404435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death of Boris |
E226549
|
entity |
| Predicate | featuresCharacter |
P626
|
FINISHED |
| Object | Feodor |
E236337
|
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: Feodor | Statement: [Death of Boris, featuresCharacter, Feodor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Feodor Context triple: [Death of Boris, featuresCharacter, Feodor]
-
A.
Fyodor
chosen
Fyodor is a masculine given name of Russian origin, most famously borne by the novelist Fyodor Dostoevsky.
-
B.
Vasily
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
C.
Rodion
Rodion is a masculine given name of Slavic origin, most notably borne by Soviet military commander Rodion Malinovsky.
-
D.
Foma Gordeyev
Foma Gordeyev is a novel by Russian writer Maksim Gorky that portrays the moral and spiritual decline of a wealthy merchant’s son amid the social tensions of late 19th-century Russia.
-
E.
Urusov
Urusov is a Russian noble family name historically associated with princely lineage and notable figures in Russian society.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51c125dc8190a6438cf0ee23e7a9 |
completed | April 1, 2026, 5:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1d59186308190b12c95d24f8486e6 |
completed | April 5, 2026, 3:22 a.m. |
Created at: March 30, 2026, 7:46 p.m.