Triple
T17552557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia River Department |
E427504
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fur-trading department |
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 department Context triple: [Columbia River Department, instanceOf, fur-trading department]
-
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.
trading post governor
A trading post governor is the official responsible for overseeing commercial activities, enforcing regulations, managing resources, and maintaining order at a frontier or colonial trading outpost.
-
D.
trading and sales division
The trading and sales division is a business unit responsible for executing financial market transactions and providing market access, products, and advisory services to clients to facilitate investment, hedging, and financing activities.
-
E.
hunting office
A hunting office is an administrative and logistical center that coordinates hunting activities, manages permits and regulations, and provides services and information to hunters within a specific region.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.