Triple
T2599192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caribbean colonies of the Dutch West India Company |
E58302
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dutch colonial possessions |
C3727
|
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: Dutch colonial possessions Context triple: [Caribbean colonies of the Dutch West India Company, instanceOf, Dutch colonial possessions]
-
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.
Dutch colonial territory
chosen
A Dutch colonial territory is a region outside Europe that was politically and economically controlled and administered by the Netherlands as part of its overseas empire.
-
C.
former Dutch colony
A former Dutch colony is a territory that was once governed, administered, or significantly controlled by the Netherlands as part of its overseas colonial empire, but has since gained independence or been transferred to another sovereignty.
-
D.
Dutch colonial province
A Dutch colonial province is an administrative region established and governed by the Netherlands in its overseas territories, typically managed by appointed colonial officials under Dutch law and economic interests.
-
E.
colonial empire
A colonial empire is a political and economic system in which a dominant state controls and exploits distant territories and their populations, typically through settlement, resource extraction, and imposed governance.
- 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_69ab4ac14040819098b13f4a27d5c8ff |
completed | March 6, 2026, 9:44 p.m. |
Created at: March 6, 2026, 9:49 p.m.