Triple
T19701373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia River Fishing and Trading Company |
E473104
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical commercial enterprise |
C4887
|
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: historical commercial enterprise Context triple: [Columbia River Fishing and Trading Company, instanceOf, historical commercial enterprise]
-
A.
historic company
chosen
A historic company is an established business organization that has operated over a significant period of time and is notable for its enduring impact, legacy, or role in historical events or developments.
-
B.
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.
-
C.
historic commercial building
A historic commercial building is a long-standing structure originally designed and used for business or trade that holds architectural, cultural, or historical significance.
-
D.
commercial historic district
A commercial historic district is a geographically defined area containing a concentration of historically significant commercial buildings and streetscapes that reflect the economic and cultural development of a community over time.
-
E.
Victorian-era business
A Victorian-era business is a commercial enterprise operating during the 19th-century Victorian period, characterized by industrialization, strict social hierarchies, emerging corporate structures, and practices shaped by imperial trade and early regulatory reforms.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:46 p.m.