Triple
T37280915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walram, Count of Jülich |
E925388
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | noble person of the Holy Roman Empire |
C63554
|
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: noble person of the Holy Roman Empire Context triple: [Walram, Count of Jülich, instanceOf, noble person of the Holy Roman Empire]
-
A.
noblewoman of the Holy Roman Empire
A noblewoman of the Holy Roman Empire is an aristocratic female member of the Empire’s hierarchical feudal society, holding status, rights, and obligations derived from her lineage, marriage, and territorial or courtly connections within its complex political structure.
-
B.
prelate of the Holy Roman Empire
A prelate of the Holy Roman Empire was a high-ranking ecclesiastical dignitary who held imperial immediacy, combining spiritual authority with temporal power as a prince of the Empire.
-
C.
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.
-
D.
medieval German statesman
A medieval German statesman is a political leader or advisor within the fragmented principalities and city-states of the Holy Roman Empire, responsible for governance, diplomacy, and the administration of law and territory.
-
E.
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.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.