Triple
T30930759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kontor of Novgorod |
E787986
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval commercial outpost |
C37673
|
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: medieval commercial outpost Context triple: [Kontor of Novgorod, instanceOf, medieval commercial outpost]
-
A.
medieval trading colony
chosen
A medieval trading colony is a distant settlement established and controlled by a city or state to facilitate long-distance commerce, resource extraction, and cultural exchange through permanent mercantile presence.
-
B.
colonial-era trading outpost
A colonial-era trading outpost is a remote settlement established by an imperial power to facilitate the exchange of goods, resources, and information between the colonizing nation and local populations, often serving as a strategic hub for commerce, governance, and cultural contact.
-
C.
maritime trading centre
A maritime trading centre is a coastal hub where goods, services, and information are exchanged via sea routes, integrating port infrastructure, commercial activities, and logistics networks to facilitate regional and international trade.
-
D.
medieval city
A medieval city is a densely populated, fortified urban center characterized by narrow winding streets, defensive walls, a central marketplace, religious and administrative buildings, and distinct social and economic quarters.
-
E.
medieval trading network
A medieval trading network is an interconnected system of routes, markets, and merchants that facilitated the exchange of goods, money, and information across regions during the Middle Ages.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:52 p.m.