Triple
T33331807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Welser concession in Venezuela |
E853425
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German colonization of the Americas |
C20131
|
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 colonization of the Americas Context triple: [Welser concession in Venezuela, instanceOf, German colonization of the Americas]
-
A.
Swedish colony
A Swedish colony is a territory outside Sweden that was settled, administered, and economically exploited under Swedish sovereignty during the period of its overseas expansion.
-
B.
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.
-
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.
European colonists
European colonists were settlers from various European nations who migrated to and established control over foreign lands, often displacing indigenous populations and exploiting local resources for economic and political gain.
-
E.
former German colony
chosen
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.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:34 a.m.