Triple
T37779588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chilean colonization law of 1845 |
E941789
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonization policy |
C1297
|
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: colonization policy Context triple: [Chilean colonization law of 1845, instanceOf, colonization policy]
-
A.
colonial policy
chosen
Colonial policy is the set of laws, strategies, and administrative practices through which a colonial power governs, exploits, and manages its colonies and their populations.
-
B.
colonization campaign
A colonization campaign is an organized, often state- or corporate-led effort to establish control, settlement, and resource exploitation in a new territory, typically involving migration, infrastructure development, and cultural or political domination over existing populations.
-
C.
colonization society
A colonization society is an organized group formed to promote, plan, and often finance the settlement of people from one region or country into another territory, typically for political, economic, or ideological purposes.
-
D.
colonialism
Colonialism is a system of domination in which a powerful state extends control over foreign territories and peoples, exploiting their resources, labor, and cultures for economic and political gain.
-
E.
colonial policy conference
A colonial policy conference is a formal gathering of scholars, policymakers, and stakeholders to analyze, debate, and shape understandings of past and present colonial governance and its enduring impacts.
- 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.