Triple
T18601815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Empire in the Pacific Northwest |
E454637
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British overseas expansion |
C31616
|
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 overseas expansion Context triple: [British Empire in the Pacific Northwest, instanceOf, British overseas expansion]
-
A.
part of British Empire expansion
chosen
A "part of British Empire expansion" represents any territory, institution, or process that contributed to the growth, consolidation, or administration of the British Empire across different regions and periods.
-
B.
colonial empire
A colonial empire is a political and economic system in which a dominant state controls and exploits distant territories and their populations, typically through settlement, resource extraction, and imposed governance.
-
C.
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.
-
D.
Portuguese conquest
Portuguese conquest refers to the series of military, maritime, and colonial expansions led by Portugal from the 15th to the 17th centuries, establishing trading posts, territories, and influence across Africa, Asia, and the Americas.
-
E.
Greek expansion
Greek expansion refers to the historical process by which Greek culture, language, political influence, and settlements spread beyond the Greek mainland into the wider Mediterranean and Near Eastern regions through colonization, conquest, and trade.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.