Triple
T5041963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal African Company |
E113565
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | English slave-trading company |
C5200
|
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: English slave-trading company Context triple: [Royal African Company, instanceOf, English slave-trading company]
-
A.
British slave-trading company
chosen
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.
chartered trading company
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.
-
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.
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.
-
E.
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.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:37 p.m.