Triple
T5683996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyotr Tolstoy |
E125266
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Tolstoy family |
C18599
|
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 Tolstoy family Context triple: [Pyotr Tolstoy, instanceOf, member of the Tolstoy family]
-
A.
member of the House of Romanov
A member of the House of Romanov is an individual belonging by birth or marriage to the former imperial dynasty that ruled Russia from 1613 until the abdication of Tsar Nicholas II in 1917.
-
B.
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.
-
C.
member of the House of Holstein-Gottorp-Romanov
A member of the House of Holstein-Gottorp-Romanov is an individual belonging to the German-Russian dynastic branch that ruled the Russian Empire from Peter III through the last tsars, combining Holstein-Gottorp and Romanov lineage.
-
D.
member of the Alcott family
A member of the Alcott family is an individual belonging by birth, marriage, or adoption to the familial lineage associated with the Alcott surname and its shared history, relationships, and traditions.
-
E.
member of the Rurik dynasty
A member of the Rurik dynasty is an individual belonging to the medieval ruling family traditionally traced to the Varangian prince Rurik, which governed parts of Eastern Europe, including Kievan Rus and later principalities, from the 9th to the 16th centuries.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:44 p.m.