Triple
T31082128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katharinenfeld |
E792127
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German settler colony |
C12591
|
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: German settler colony Context triple: [Katharinenfeld, instanceOf, German settler colony]
-
A.
Dutch colony
A Dutch colony is a territory politically and economically controlled by the Netherlands, established primarily for trade, resource extraction, and strategic influence during the era of European imperial expansion.
-
B.
former German colony
A former German colony is a territory that was once under the political control and administration of the German Empire or later German states, but has since gained independence or come under another sovereignty.
-
C.
Prussian colony
A Prussian colony is a territory politically and administratively controlled by the Kingdom of Prussia, typically acquired through conquest, diplomacy, or settlement, and governed to serve Prussian strategic, economic, and cultural interests.
-
D.
former colonial settlement
chosen
A former colonial settlement is a community or territory originally established and governed by a foreign colonial power that has since transitioned to local or independent control, often retaining cultural, architectural, and institutional legacies of its colonial past.
-
E.
historical Boer republic
A historical Boer republic is a 19th- to early 20th-century self-governing state established in southern Africa by Dutch-speaking settlers (Boers) seeking political independence from British colonial rule.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:02 p.m.