Triple
T8597903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asiatisk Kompagni |
E203596
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Danish trading company |
C14737
|
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: Danish trading company Context triple: [Asiatisk Kompagni, instanceOf, Danish trading company]
-
A.
British slave-trading company
A British slave-trading company is a commercial enterprise, chartered or based in Britain, that organized, financed, and profited from the capture, transport, and sale of enslaved Africans across the Atlantic.
-
B.
Danish company
A Danish company is a business entity established and operating under the laws of Denmark, typically registered with the Danish Business Authority and subject to Danish corporate, tax, and employment regulations.
-
C.
chartered trading company
chosen
A chartered trading company is a business organization granted exclusive rights and privileges by a government charter to conduct trade, often in specific regions or commodities, typically during the early modern period.
-
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.
Dutch company
A Dutch company is a business entity established under the laws of the Netherlands, typically registered with the Dutch Chamber of Commerce and subject to Dutch corporate, tax, and regulatory frameworks.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:24 p.m.