Triple
T34914040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herkus Monte |
E1006952
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prussian noble |
C61855
|
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: Prussian noble Context triple: [Herkus Monte, instanceOf, Prussian noble]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
9th-century German noble
A 9th-century German noble was a member of the hereditary warrior aristocracy in the East Frankish realms, holding land and local authority in exchange for military service and loyalty to the Carolingian king or his successors.
-
E.
Prussian royal
A Prussian royal is a member of the ruling Hohenzollern dynasty or its close relatives who held hereditary titles and exercised or symbolized monarchical authority in the Kingdom of Prussia.
- 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.