Triple
T11880284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Tobago |
E282640
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | territory of the Dutch West India Company |
C2644
|
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: territory of the Dutch West India Company Context triple: [Dutch Tobago, instanceOf, territory of the Dutch West India Company]
-
A.
Dutch colonial territory
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.
-
B.
Dutch colony
chosen
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.
organ of the Dutch West India Company
An organ of the Dutch West India Company is any official governing, administrative, or executive body (such as the directors, chambers, or councils) through which the Company exercised its legal powers and conducted its affairs.
-
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.
Dutch trading post
A Dutch trading post is a commercial outpost established by the Dutch, primarily during the 17th and 18th centuries, to facilitate trade, resource extraction, and colonial administration in foreign territories.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:44 p.m.