Triple
T20810643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Saxe-Hildburghausen |
E512287
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German princely title |
C43784
|
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 princely title Context triple: [Prince of Saxe-Hildburghausen, instanceOf, German princely 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.
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.
-
E.
member of German nobility
A member of German nobility is an individual belonging to a historically privileged social class in German-speaking regions, typically holding hereditary titles, land, and social status recognized under traditional aristocratic systems.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:40 p.m.