Triple
T34919689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British South Africa Company rule in Matabeleland |
E1007101
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | chartered company colonial administration |
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: chartered company colonial administration Context triple: [British South Africa Company rule in Matabeleland, instanceOf, chartered company colonial administration]
-
A.
colonial enterprise
A colonial enterprise is an organized venture, typically led by a state or chartered company, that establishes control over foreign territories and peoples to extract resources, labor, and strategic advantage.
-
B.
royal chartered company
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.
-
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.
colonial governing charter
A colonial governing charter is a formal legal document issued by a sovereign power that establishes the framework, authority, and rules by which a colony is organized and governed.
-
E.
empresario colony
An empresario colony is a settlement established in a region (notably in Mexican Texas) by a private individual or contractor granted land and authority by a government to recruit and manage colonists.
- 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.