Triple
T29612377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yermolai Solzhenitsyn |
E754761
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Solzhenitsyn family |
C55967
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: member of the Solzhenitsyn family Context triple: [Yermolai Solzhenitsyn, instanceOf, member of the Solzhenitsyn family]
-
A.
member of the Tolstoy family
A member of the Tolstoy family is an individual belonging by birth or marriage to the historically significant Russian noble lineage associated with the writer Leo Tolstoy and his relatives.
-
B.
member of the Godunov family
A member of the Godunov family is an individual belonging to a historically significant Russian noble lineage, often associated with political influence, landownership, and cultural heritage in Russia.
-
C.
Romanov family member
A Romanov family member is an individual belonging by birth or marriage to the Russian imperial dynasty that ruled Russia from 1613 until the abdication of Tsar Nicholas II in 1917.
-
D.
member of the Shuisky family
A member of the Shuisky family is an individual belonging to the powerful Russian noble lineage that played significant political and dynastic roles, particularly during the late Rurikid and Time of Troubles periods.
-
E.
member of the Demidov family
A member of the Demidov family is an individual belonging by birth or legal relation to the historically significant Demidov lineage, known for its influence, wealth, and social standing.
- F. None of above. chosen
Provenance (1 batch)
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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:29 p.m.