Triple
T33540501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Roman Emperors of the Luxembourg dynasty |
E859056
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Holy Roman Emperors by dynasty |
C32064
|
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: Holy Roman Emperors by dynasty Context triple: [Holy Roman Emperors of the Luxembourg dynasty, instanceOf, Holy Roman Emperors by dynasty]
-
A.
Nuremberg dynasty
The Nuremberg dynasty is a conceptual class representing a lineage of influential families or rulers centered in or originating from Nuremberg, whose power, heritage, and socio-political impact persist across multiple generations.
-
B.
Habsburg
Habsburg: A powerful European royal dynasty that ruled vast territories including the Holy Roman Empire, Spain, and Austria for centuries through strategic marriages and political alliances.
-
C.
Hohenstaufen
chosen
Hohenstaufen is a medieval German royal and imperial dynasty that ruled the Holy Roman Empire and parts of Italy and Sicily between the 12th and 13th centuries.
-
D.
Habsburg monarch
A Habsburg monarch is a sovereign ruler from the Habsburg dynasty, which dominated Central European and Spanish thrones for centuries through strategic marriages and dynastic inheritance.
-
E.
King of the Romans
The King of the Romans was the title used by the elected ruler of the Holy Roman Empire, designating him as emperor-designate pending papal coronation as Holy Roman Emperor.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.