Triple
T15013081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Brunswick-Bevern |
E377887
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German ducal title |
C2995
|
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: German ducal title Context triple: [Duke of Brunswick-Bevern, instanceOf, German ducal title]
-
A.
German princely dynasty
A German princely dynasty is a hereditary ruling family from the German-speaking regions of Europe that historically held princely titles, governed territories, and played significant roles in regional and imperial politics.
-
B.
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.
-
C.
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.
-
D.
German noble
chosen
A German noble is a member of the historical aristocratic class in German-speaking regions, traditionally holding hereditary titles, land, and social privileges within the feudal and later monarchical systems.
-
E.
Dutch noble title
A Dutch noble title is a hereditary or granted rank within the Netherlands’ nobility system, such as baron, count, or duke, conferring social prestige and sometimes traditional privileges but no formal political power today.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:55 a.m.