Triple
T8373316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Pavlovich of Russia |
E197511
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century Russian noble |
C20725
|
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: 19th-century Russian noble Context triple: [Michael Pavlovich of Russia, instanceOf, 19th-century Russian noble]
-
A.
Russian noblewoman
A Russian noblewoman is an aristocratic woman of the Russian Empire or nobility, typically distinguished by her high social rank, landowning family background, and participation in elite cultural and political life.
-
B.
Russian prince
chosen
A Russian prince is a male noble of princely rank in Russia, historically belonging to the aristocratic ruling class and often holding political, military, or territorial authority within the Russian Empire or its predecessor states.
-
C.
Russian grand duchess
A Russian grand duchess is a female member of the Russian imperial family, typically the daughter or granddaughter of a tsar, holding high noble rank and associated with significant social and political status in the Russian Empire.
-
D.
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.
-
E.
Baltic German noble
A Baltic German noble was a member of the German-speaking hereditary elite in the Baltic provinces (primarily present-day Estonia and Latvia), historically holding significant land, political power, and cultural influence under various ruling empires.
- F. None of above.
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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 6:01 p.m.