Triple
T27320133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Karl Theodor von Wrede |
E689467
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bavarian nobleman |
C9089
|
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: Bavarian nobleman Context triple: [Prince Karl Theodor von Wrede, instanceOf, Bavarian nobleman]
-
A.
Bavarian prince
chosen
A Bavarian prince is a male member of the royal or formerly ruling house of Bavaria, traditionally holding hereditary titles, privileges, and social status within the region’s historical monarchy.
-
B.
Austrian noble
An Austrian noble is a member of the historical aristocracy of Austria, typically holding hereditary titles, land, and social privileges within the Habsburg and later Austrian realms.
-
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.
19th-century German nobleman
A 19th-century German nobleman is an aristocratic landowner and social elite in the fragmented German states or later the German Empire, wielding hereditary titles, political influence, and economic power within a rigid hierarchical society undergoing rapid industrial and national transformation.
-
E.
Bavarian monarch
A Bavarian monarch is the sovereign ruler of Bavaria, historically holding supreme political authority and symbolic leadership over the Bavarian state and its people.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 11:32 a.m.