Triple
T31325507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timotheus von Bock |
E798873
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Baltic German nobleman |
C22805
|
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: Baltic German nobleman Context triple: [Timotheus von Bock, instanceOf, Baltic German nobleman]
-
A.
Baltic German noble
chosen
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.
-
B.
German-Russian nobleman
A German-Russian nobleman is an aristocrat of German origin or heritage who held social status, land, or titles within the Russian Empire, often serving in its military, administrative, or courtly institutions.
-
C.
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.
-
D.
Polish–Lithuanian nobleman
A Polish–Lithuanian nobleman was a member of the szlachta elite of the Polish–Lithuanian Commonwealth, holding hereditary privileges, political rights, and often landed estates within its multiethnic realm.
-
E.
Lithuanian noble
A Lithuanian noble is a member of the historical aristocratic class of the Grand Duchy of Lithuania (and later the Polish–Lithuanian Commonwealth), holding hereditary titles, land, and political privileges within the region’s feudal and early modern social hierarchy.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:15 p.m.