Triple
T6994519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Cleves |
E162175
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical German principality |
C17262
|
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: historical German principality Context triple: [Duchy of Cleves, instanceOf, historical German principality]
-
A.
constituent state of the German Empire
A constituent state of the German Empire was one of the semi-autonomous kingdoms, grand duchies, duchies, principalities, free Hanseatic cities, or imperial territories that together formed the federal structure of the German Empire from 1871 to 1918.
-
B.
former Prussian city
A former Prussian city is an urban settlement that historically belonged to the Kingdom of Prussia or the later Prussian state but now lies within the borders of a different modern nation.
-
C.
hereditary principality
chosen
A hereditary principality is a sovereign or semi-sovereign territory ruled by a prince whose authority and title are passed down through a family line, typically by primogeniture or other dynastic succession rules.
-
D.
Ernestine duchy
The Ernestine duchy refers to any of the small, historically fragmented German principalities in Thuringia ruled by the Ernestine branch of the Wettin dynasty after the partition of Saxony.
-
E.
province of Prussia
A province of Prussia was a major administrative territorial unit within the Kingdom (and later state) of Prussia, serving as a top-level regional division for governance, law, and administration.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:32 p.m.