Triple
T19613799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Niger Company |
E470804
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British trading company |
C41525
|
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: British trading company Context triple: [Royal Niger Company, instanceOf, British 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.
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.
19th-century British company
A 19th-century British company is a business organization established in Britain between 1801 and 1900, typically operating under early industrial capitalism, imperial trade networks, and evolving corporate and legal frameworks of the Victorian era.
-
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.
royal chartered company
chosen
A royal chartered company is a business organization established and granted special rights, privileges, and legal status by a monarch through a formal charter, often to conduct trade or colonization.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
Created at: April 10, 2026, 1:43 p.m.