Triple
T12589285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leopold I, Duke of Lorraine |
E300558
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ruler of Lorraine |
C8067
|
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 of Lorraine Context triple: [Leopold I, Duke of Lorraine, instanceOf, ruler of Lorraine]
-
A.
Duke of Lorraine
chosen
The Duke of Lorraine is a noble title historically held by the sovereign ruler of the Duchy of Lorraine, a strategically important region in northeastern France that played a key role in European dynastic and territorial politics.
-
B.
King of Lotharingia
The King of Lotharingia is the sovereign ruler of the medieval kingdom of Lotharingia, governing its territories, administering justice, leading its armies, and representing its authority within the broader context of the Frankish and later Holy Roman Empire realms.
-
C.
Duke of Lotharingia
The Duke of Lotharingia is a high-ranking noble who governs the historical region of Lotharingia, wielding military, judicial, and administrative authority on behalf of the sovereign.
-
D.
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.
-
E.
Regent of France
A Regent of France is an individual appointed to govern the kingdom temporarily on behalf of a monarch who is unable to rule, typically due to minority, absence, or incapacity.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:06 p.m.