Triple
T10140250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodosia Igorevna of Ryazan |
E226962
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Rus' 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: medieval Rus' noble Context triple: [Theodosia Igorevna of Ryazan, instanceOf, medieval Rus' noble]
-
A.
Finnish noble
A Finnish noble is a member of the historical aristocratic class in Finland, traditionally holding hereditary titles, land, and social privileges recognized by the Swedish and later Russian crowns, and organized through institutions such as the Finnish House of Nobility.
-
B.
nobleman
A nobleman is a male member of the aristocracy who holds a hereditary or granted title, social privileges, and often land or political influence within a hierarchical society.
-
C.
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.
-
D.
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.
-
E.
Finnish nobleman
A Finnish nobleman is a male member of Finland’s historical nobility, typically holding hereditary titles, land, and social status recognized under the Swedish and later Russian rule, and often involved in military, administrative, or political leadership.
- 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_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 9:07 p.m.