Triple
T15251686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dejima trading post |
E364532
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dutch trading post in Japan |
C11167
|
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 trading post in Japan Context triple: [Dejima trading post, instanceOf, Dutch trading post in Japan]
-
A.
Dutch trading post
chosen
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.
-
B.
Portuguese trading post
A Portuguese trading post is a fortified coastal or riverside settlement established by Portugal during the Age of Exploration to control trade routes, facilitate commerce, and project imperial influence.
-
C.
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.
-
D.
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.
-
E.
Bugis principality
A Bugis principality is a traditional political entity or small sovereign state historically governed by Bugis rulers in South Sulawesi, Indonesia, characterized by its own leadership, territory, and customary laws.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:13 a.m.