Triple
T1983896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Duchy of Saxe-Weimar-Eisenach |
E43093
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member state of the German Confederation |
C10828
|
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: member state of the German Confederation Context triple: [Grand Duchy of Saxe-Weimar-Eisenach, instanceOf, member state of the German Confederation]
-
A.
state of Germany
A state of Germany is a federal constituent entity (Bundesland) with its own government, constitution, and administrative responsibilities within the Federal Republic of Germany.
-
B.
federal state of Germany
A federal state of Germany is a constituent political entity within the Federal Republic of Germany that possesses its own government, constitution, and legislative powers under the framework of the German federal system.
-
C.
federal state of Austria
A federal state of Austria is one of the nine constituent political and administrative regions that together form the Republic of Austria, each with its own government and specific constitutional powers.
-
D.
confederation of states
A confederation of states is a union of sovereign states that voluntarily cooperate on certain common matters through a central body that has limited authority and depends on the member states for implementation and enforcement.
-
E.
constituent country
A constituent country is a semi-autonomous nation within a larger sovereign state, possessing its own government and identity while sharing overarching sovereignty and institutions with the parent state.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:37 p.m.