Triple
T18321104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principality of Minden |
E438880
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | secular principality |
C3295
|
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: secular principality Context triple: [Principality of Minden, instanceOf, secular principality]
-
A.
hereditary principality
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.
-
B.
Grand Duchy
A Grand Duchy is a sovereign or semi-sovereign state or territory ruled by a grand duke or grand duchess, ranking below a kingdom but above a duchy in traditional European nobility hierarchies.
-
C.
Piast-ruled principality
A Piast-ruled principality is a medieval territorial polity in Central Europe governed by a member of the Piast dynasty, typically characterized by fragmented authority, hereditary rule, and integration into the broader political landscape of the Polish and neighboring realms.
-
D.
subnational monarchy
A subnational monarchy is a monarchical system of governance that exists within and is subordinate to a larger sovereign state, where a monarch rules a specific region, province, or territory under the overarching authority of the national government.
-
E.
vassal state
chosen
A vassal state is a subordinate political entity that retains limited internal autonomy while owing allegiance, tribute, or military support to a more powerful sovereign state.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:36 a.m.