Triple
T35202979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VOC governor-general |
E1016458
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | office in the Dutch East India Company |
C63700
|
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: office in the Dutch East India Company Context triple: [VOC governor-general, instanceOf, office in the Dutch East India Company]
-
A.
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.
-
B.
organ of the British East India Company
An organ of the British East India Company is any official body, office, or instrument through which the Company exercised its administrative, commercial, or political functions.
-
C.
Dutch East India Company ship
A Dutch East India Company ship is a large, ocean-going sailing vessel used by the VOC in the 17th and 18th centuries to transport spices, goods, and people between Europe and Asia while serving both commercial and military purposes.
-
D.
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.
-
E.
Dutch colonial figure
A Dutch colonial figure is an individual from the Netherlands who played a significant role in the administration, expansion, or cultural impact of Dutch overseas territories during the colonial period.
- F. None of above. chosen
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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.