Triple
T26190583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick Augustus II, Elector of Saxony |
E654950
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 18th-century German prince |
C51217
|
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: 18th-century German prince Context triple: [Frederick Augustus II, Elector of Saxony, instanceOf, 18th-century German prince]
-
A.
former German prince
A former German prince is an individual who once held, but no longer possesses, a princely title within the historical German nobility, typically due to political, legal, or dynastic changes.
-
B.
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.
-
C.
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.
-
D.
Bavarian prince
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.
-
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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 8:44 p.m.