Triple
T8402522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian II, Count Palatine of Zweibrücken-Birkenfeld |
E198408
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nobleman of the Holy Roman Empire |
C1905
|
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: nobleman of the Holy Roman Empire Context triple: [Christian II, Count Palatine of Zweibrücken-Birkenfeld, instanceOf, nobleman of the Holy Roman Empire]
-
A.
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.
-
B.
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.
-
C.
Prince-elector of the Holy Roman Empire
A Prince-elector of the Holy Roman Empire was a high-ranking territorial ruler or ecclesiastical prince endowed with the exclusive right to participate in the election of the Holy Roman Emperor.
-
D.
nobleman
chosen
A nobleman is a male member of the aristocracy who holds a hereditary or granted title, social privileges, and often land or political influence within a hierarchical society.
-
E.
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.
- 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_69ca8310df9c8190b25f16161cca3e41 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:04 p.m.