Triple
T34767086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leopold Clement, Hereditary Prince of Lorraine |
E1002247
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hereditary Prince of Lorraine |
C61990
|
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: Hereditary Prince of Lorraine Context triple: [Leopold Clement, Hereditary Prince of Lorraine, instanceOf, Hereditary Prince of Lorraine]
-
A.
Luxembourgian prince
A Luxembourgian prince is a male member of the Grand Ducal Family of Luxembourg who holds the princely title by birth or marriage within the country's constitutional monarchy.
-
B.
hereditary grand duke
A hereditary grand duke is a noble ruler who holds the grand ducal title by birthright, passing it down through a recognized line of succession within a grand duchy or equivalent realm.
-
C.
Duke of Luxembourg
The Duke of Luxembourg is a noble title historically associated with the ruler or high-ranking aristocrat of the Luxembourg region, often linked to European dynastic and political affairs.
-
D.
Duke of Lorraine
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.
-
E.
Capetian prince
A Capetian prince is a male royal born into or descended from the Capetian dynasty, traditionally holding the title and status of a king’s son or close male relative within that ruling house.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.