Triple
T14033997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vosporo |
E337662
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trading outpost |
C30402
|
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: trading outpost Context triple: [Vosporo, instanceOf, trading outpost]
-
A.
trading empire
A trading empire is a vast, interconnected commercial domain that dominates long-distance exchange of goods, capital, and information across multiple regions or cultures, often shaping political power and economic systems in its sphere of influence.
-
B.
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.
-
C.
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.
-
D.
trading fort
chosen
A trading fort is a fortified outpost established to protect and facilitate commercial exchange, typically serving as a secure hub where merchants, goods, and local populations converge for trade.
-
E.
transoceanic trade network
A transoceanic trade network is a system of interconnected maritime routes, ports, merchants, and institutions that facilitate the large-scale exchange of goods, people, capital, and ideas across oceans between distant regions of the world.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:20 p.m.