Triple
T1577776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confederation of the Rhine |
E33692
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Napoleonic client state |
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: Napoleonic client state Context triple: [Confederation of the Rhine, instanceOf, Napoleonic client state]
-
A.
Napoleonic policy
Napoleonic policy refers to the strategic, administrative, legal, and military measures implemented by Napoleon Bonaparte to centralize authority, modernize state institutions, expand French influence, and consolidate his personal rule across Europe.
-
B.
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.
-
C.
imperial confederation
An imperial confederation is a loose union of semi-autonomous states or territories under the overarching authority of an empire, which coordinates common policies while allowing substantial local self-rule.
-
D.
former sovereign state
A former sovereign state is a political entity that once possessed full independence and international recognition as a nation but has since lost that status through dissolution, merger, annexation, or other political change.
-
E.
dynastic empire
A dynastic empire is a vast, centralized state ruled over generations by a single family lineage that legitimizes its authority through hereditary succession and often divine or traditional claims to power.
- 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_69a885f27a4c8190a4622252cdf54c00 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:27 p.m.