Triple
T1983895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Duchy of Saxe-Weimar-Eisenach |
E43093
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | constituent state of the German Empire |
C10827
|
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: constituent state of the German Empire Context triple: [Grand Duchy of Saxe-Weimar-Eisenach, instanceOf, constituent state of the German Empire]
-
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.
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.
-
D.
province of Prussia
A province of Prussia was a major administrative and territorial division within the Kingdom (and later Free State) of Prussia, functioning as a regional unit of government with its own local authorities under the broader Prussian state.
-
E.
administrative region of Germany
An administrative region of Germany is a territorial unit within a federal state (Land) that serves as an intermediate level of government for coordinating regional administration, planning, and public services.
- 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.