Triple
T17265083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsarevich Ilya Fyodorovich |
E419103
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian royal prince |
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: Russian royal prince Context triple: [Tsarevich Ilya Fyodorovich, instanceOf, Russian royal prince]
-
A.
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.
-
B.
Georgian prince
A Georgian prince is a male member of the royal or noble families of Georgia, historically holding hereditary titles, political influence, and social prestige within the Georgian monarchy and aristocracy.
-
C.
Prussian prince
A Prussian prince is a male royal family member of the Kingdom of Prussia, typically holding hereditary titles, political influence, and social prestige within the Prussian and broader German nobility.
-
D.
Christian prince
A Christian prince is a sovereign or ruling noble whose authority and governance are explicitly shaped by Christian beliefs, values, and ecclesiastical relationships.
-
E.
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.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:40 a.m.