Triple
T20412998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lothar I |
E500635
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Holy Roman Emperor (predecessor concept) |
C12342
|
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 Emperor (predecessor concept) Context triple: [Lothar I, instanceOf, Holy Roman Emperor (predecessor concept)]
-
A.
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.
-
B.
imperial state of the Holy Roman Empire
An imperial state of the Holy Roman Empire was a semi-autonomous political entity—such as a duchy, principality, city, or ecclesiastical territory—directly subject to the authority of the emperor and the imperial diet rather than to any intermediate lord.
-
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.
Frankish emperor
chosen
A Frankish emperor is a sovereign ruler from the Frankish people who held imperial authority in Western and Central Europe, most notably exemplified by Charlemagne and his successors in the early Middle Ages.
-
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.
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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:30 a.m.