Triple
T23927011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia District |
E602385
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fur trading district |
C28385
|
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: fur trading district Context triple: [Columbia District, instanceOf, fur trading district]
-
A.
fur-trading administrative district
chosen
A fur-trading administrative district is a geographically defined territory managed by a trading company or authority to regulate, oversee, and profit from the organized exchange of animal pelts and related goods.
-
B.
fur trading post
A fur trading post is a remote commercial outpost where trappers, Indigenous peoples, and traders exchanged animal pelts for goods such as tools, weapons, textiles, and provisions.
-
C.
frontier post
A frontier post is a fortified or administrative outpost located at the edge of a state’s or empire’s territory, serving to monitor, defend, and control movement across its borders.
-
D.
frontier province
A frontier province is a border region of a state or empire where central authority, culture, and control meet and interact with external or less-governed territories, often marked by strategic, economic, and cultural significance.
-
E.
frontier region
A frontier region is a sparsely settled, transitional area at the edge of established territories where political control, cultural influences, and economic systems are fluid and contested.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
Created at: April 17, 2026, 8:48 p.m.