Triple
T38289940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian–Russian Pomor trade region |
E1022329
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic trade region |
C263
|
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: historic trade region Context triple: [Norwegian–Russian Pomor trade region, instanceOf, historic trade region]
-
A.
historic region
chosen
A historic region is a geographically defined area recognized for its significant past events, cultural heritage, or historical identity that has shaped its development over time.
-
B.
historical trade center
A historical trade center is a geographically strategic hub where merchants, goods, cultures, and ideas converged over time, driving regional economic activity and cross-cultural exchange.
-
C.
colonial-era trade corridor
A colonial-era trade corridor is a strategically established route or network used during colonial times to transport goods, people, and resources between colonies and imperial centers, shaping economic patterns and cultural exchanges.
-
D.
ancient trade route
An ancient trade route is a historically established pathway or network used for the long-distance exchange of goods, ideas, cultures, and technologies between regions and civilizations.
-
E.
history of a region
A history of a region is a structured account of the social, political, economic, and cultural developments that have shaped a specific geographic area over time.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.