Triple
T24939869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gustavus of Zweibrücken-Kleeburg |
E623418
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Palatine prince |
C19495
|
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: Palatine prince Context triple: [Gustavus of Zweibrücken-Kleeburg, instanceOf, Palatine prince]
-
A.
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.
-
B.
Christian prince
A Christian prince is a sovereign or ruling noble whose authority and governance are explicitly shaped by Christian beliefs, values, and ecclesiastical relationships.
-
C.
Count Palatine
chosen
A Count Palatine is a noble title historically granted to a count who exercised sovereign or semi-sovereign authority within their territory, often with special judicial and administrative powers delegated directly by a monarch or emperor.
-
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.
prince of the Holy Roman Empire
A prince of the Holy Roman Empire was a secular or ecclesiastical ruler who held immediate authority under the emperor, possessing territorial sovereignty and a vote in the Imperial Diet.
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:30 a.m.