Triple
T21096355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick VII of Denmark |
E519777
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Lauenburg |
C44243
|
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: Duke of Lauenburg Context triple: [Frederick VII of Denmark, instanceOf, Duke of Lauenburg]
-
A.
Duke of Holstein-Gottorp
The Duke of Holstein-Gottorp was the hereditary ruler of the ducal share of the duchy of Holstein (and often Schleswig), a German princely title held by a cadet branch of the Oldenburg dynasty that played a significant role in Northern European and Scandinavian politics.
-
B.
Duke of Brunswick-Lüneburg
The Duke of Brunswick-Lüneburg was a title held by various princes of the Holy Roman Empire who ruled over the duchy of Brunswick-Lüneburg in what is now northern Germany, often dividing and reuniting its territories among different dynastic lines.
-
C.
Duke of Saxony
The Duke of Saxony is a high-ranking noble title historically held by rulers of the Saxony region in present-day Germany, signifying territorial authority, military leadership, and political influence within the Holy Roman Empire and later German states.
-
D.
Duke of Elchingen
The Duke of Elchingen is a noble title historically associated with a high-ranking military leader, notably held by Marshal Michel Ney of Napoleonic France.
-
E.
Duke of Courland
The Duke of Courland was the hereditary ruler of the Duchy of Courland and Semigallia, a semi-autonomous Baltic state under Polish-Lithuanian suzerainty from the 16th to 18th centuries.
- 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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:52 p.m.