Triple
T16929178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernst of Bavaria |
E410657
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ruler in the Holy Roman Empire |
C12473
|
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: ruler in the Holy Roman Empire Context triple: [Ernst of Bavaria, instanceOf, ruler in the Holy Roman Empire]
-
A.
office of the Holy Roman Empire
The office of the Holy Roman Empire is a formal position within the imperial hierarchy responsible for specific administrative, judicial, ceremonial, or territorial duties under the authority of the Holy Roman Emperor.
-
B.
prince of the Holy Roman Empire
chosen
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.
ruler of Further Austria
The ruler of Further Austria was the Habsburg sovereign who governed the scattered western Austrian territories in Swabia, Alsace, and adjacent regions, often as a secondary or appanage domain to the main Austrian or imperial crown.
-
D.
constitutional instrument of the Holy Roman Empire
A constitutional instrument of the Holy Roman Empire is a formal legal act—such as a decree, charter, or treaty—that defined, modified, or clarified the Empire’s constitutional structure, powers, and relationships among its emperor, princes, and estates.
-
E.
ruler of Tyrol
A ruler of Tyrol is the sovereign or governing authority who holds political and administrative power over the historical region of Tyrol in the Alps.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:30 a.m.