Triple
T2845102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichsgau Wartheland |
E62564
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Reichsgau |
C7692
|
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: Reichsgau Context triple: [Reichsgau Wartheland, instanceOf, Reichsgau]
-
A.
administrative region of Bavaria
An administrative region of Bavaria is a territorial subdivision within the German state of Bavaria that serves as an intermediate level of government, coordinating regional administration, planning, and public services across its constituent districts and municipalities.
-
B.
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.
-
C.
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.
-
D.
region of Bavaria
A region of Bavaria is a geographically and administratively defined area within the German federal state of Bavaria, characterized by shared cultural, historical, and economic features.
-
E.
region of Germany
chosen
A region of Germany is a geographically and culturally distinct area within the country, often defined by historical boundaries, administrative divisions, or shared economic and social characteristics.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
Created at: March 6, 2026, 10:02 p.m.